aboutsummaryrefslogtreecommitdiffstats
path: root/org.eclipse.jgit.pgm.test/src
diff options
context:
space:
mode:
authorAndrey Loskutov <loskutov@gmx.de>2015-10-27 23:51:21 +0100
committerAndrey Loskutov <loskutov@gmx.de>2015-10-28 00:02:41 +0100
commit79a7dd026fa393fa3c66e945839e9faef744be2f (patch)
treef1220255bf3dc58c29c198b147dd0a50df553aec /org.eclipse.jgit.pgm.test/src
parent94e31bc4789894f77094a671c439fef7a51f495a (diff)
downloadjgit-79a7dd026fa393fa3c66e945839e9faef744be2f.tar.gz
jgit-79a7dd026fa393fa3c66e945839e9faef744be2f.zip
[performance] Remove synthetic access$ methods in pack and file packages
Java compiler must generate synthetic access methods for private methods and fields of the enclosing class if they are accessed from inner classes and vice versa. While invisible in the code, those synthetic access methods exist in the bytecode and seem to produce some extra execution overhead at runtime (compared with the direct access to this fields or methods), see https://git.eclipse.org/r/58948/. By removing the "private" access modifier from affected methods and fields we help compiler to avoid generation of synthetic access methods and hope to improve execution performance. To validate changes, one can either use javap or use Bytecode Outline plugin in Eclipse. In both cases one should look for "synthetic access$<number>" methods at the end of the class and inner class files in question - there should be none. NB: don't mix this "synthetic access$" methods up with "public synthetic bridge" methods generated to allow generic method override return types. Change-Id: If53ec94145bae47b74e2561305afe6098012715c Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
Diffstat (limited to 'org.eclipse.jgit.pgm.test/src')
0 files changed, 0 insertions, 0 deletions