Bug 343978 - optimize for certain cases of thisJoinPoint usage
Summary: optimize for certain cases of thisJoinPoint usage
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.6.11   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 11:09 EDT by Andrew Clement CLA
Modified: 2011-04-27 11:09 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Clement CLA 2011-04-27 11:09:10 EDT 
For the simple (common) case of some advice calling 'thisJoinPoint.getTarget()' or similar, we could avoid building the entire tjp object at the jp location.  If we say the optimization isn't allowed if you:

- assign tjp to something in the advice
- pass tjp onto another method

then I still think we'd cover a lot of scenarios.  Building the array of arguments is probably very expensive and if not used in the advice, that is a big waste.