| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
JVM improvements seem to reduce the difference.
|
| |
|
|
| |
concrete sub-aspect exists in the world
|
| |
|
|
|
|
| |
Bugzilla Bug 75568 : ajc changes classfile timestamps even if compilation fails (regression)
and maybe:
Bugzilla Bug 74245: -proceedOnError does not weave aspects on compile error
|
| |
|
|
| |
Load Time Weaving aborts on any kind of warning (declare/xlint)
|
| |
|
|
| |
Weaving class loader
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lazy instantiation of thisJoinPoint
Speed-ups of 10-100X are measured even when running a small test case with minimal GC issues.
The actual feature implemented is that thisJoinPoint objects are only created just before calling the method for advice that requires them. To take advantage of this feature you must use an if PCD or some other dynamic test that occurs in the PCD not the advice body to guard the expensive creation of the thisJoinPoint object.
-XlazyTjp flag must be passed to compiler to enable this feature.
If any around advice is present on the joinpoint then lazy instantiation
will be disabled. An Xlint warning will be displayed in this case.
As a related optimization, several helper methods were added to
Factory.makeJP to reduce the code size when thisJoinPoint is used.
|
| |
|
|
| |
number of loops in BasicCommandTestCase.testSizeChanges()
|
| |
|
|
| |
ajc needs -d . option while correctly compiling classes from subpackage
|
| | |
|
| | |
|
| |
|
|
| |
ajc -aspectpath fails with NPE for cflow pointcuts
|
| |
|
|
| |
weave performance with and without it
|
| |
|
|
|
|
| |
behavior
for obvious forms of abstract aspects now
|
| |
|
|
| |
for obvious forms of concrete aspects, next need to address abstract
|
| | |
|
| | |
|
| |
|
