aboutsummaryrefslogtreecommitdiffstats
path: root/weaver/testdata/TjpBeforeHelloWorld.txt
Commit message (Collapse)AuthorAgeFilesLines
* Various changes to get tests passing on 1.8 and 1.9Andy Clement2017-09-241-4/+4
|
* optimizations: working with Abraham on these: this one avoids trailing ':' ↵aclement2010-08-171-4/+4
| | | | which will create a CP hit more frequently.
* more overweaving tests and fixes: method call/field get/setaclement2010-05-131-4/+9
|
* 231396: refactoring AspectJ: Due to PMD reported problem in Utility - had to ↵aclement2008-06-041-1/+1
| | | | change expected code
* test and fixes for 145442 - line number info for stack traces.aclement2006-09-281-2/+2
|
* tests and implementation for enh 147711 (use true synthetic attribute/flag ↵acolyer2006-06-241-5/+5
| | | | for aj synthetic members).
* fix for pr59076, much more memory efficient creation of join point static partsacolyer2005-09-011-8/+27
|
* Fix for Bugzilla Bug 41181 aclement2004-03-161-4/+4
| | | | | Support SerialVersionUID field if no new fields declared on class (Regenerated with BcweaverJarMaker)
* Implemented feature for Bugzilla Bug 48091 jhugunin2004-01-241-35/+13
| | | | | | | | | | | | | | 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.
* Updated expected bytecode to match change for fix for issue of jhugunin2003-05-011-1/+1
| | | | Class.forName differences between IBM and SUN's JDKs
* initial versionwisberg2002-12-161-0/+129