object header in codeinfo vs. methodinfo
Update: We had too much problems with this patch, so I simply reverted it: http://b2.complang.tuwien.ac.at/cgi-bin/viewcvs.cgi?rev=7575&view=rev
Commit: http://b2.complang.tuwien.ac.at/cgi-bin/viewcvs.cgi?rev=7268&view=rev
If we use a object header in the codeinfo structure rather than in the methodinfo structure, we can save some memory, since much more methods are actually loaded than really compiled.
This will also help us when changing the way patchers are called (we will then use the implementation specific lock for all patchers).
This is with GNU Classpath 0.94-pre (31. Jan 2007).
32-bit (powerpc)
props
loaded methods : 4922
compiled methods: 1182
methodinfo (100 B): 492200
codeinfo ( 48 B): 60432
methodinfo ( 88 B): 433136 (-59064)
codeinfo ( 64 B): 80576 (+20144)
--------
-38920
eclipse
loaded methods : 54923
compiled methods: 22563
methodinfo (100 B): 5492300
codeinfo ( 48 B): 1134000
methodinfo ( 88 B): 4833664 (-658636)
codeinfo ( 64 B): 1512896 (+378896)
---------
-279740