[Bug java/18190] [4.0 regression] primitive array optimization is gone

[mckinlay at redhat dot com]

------- Additional Comments From mckinlay at redhat dot com  2004-11-04 18:46 -------
Here's my thoughts about this:

- This optimization only ever worked for source compilation. Bytecode compilers
always emit array initializers as code, so for byte compilation it makes no
difference.

- I don't see a strong reason not to reference the vtable symbols, but if we
decide to remove my patch then we need to be careful that the original bug
remains fixed - see: http://gcc.gnu.org/ml/java-patches/2004-q3/msg00343.html

- Is this optimization really worth worrying about? I'm pretty sure that
performance-wise, the difference is insignificant - binary size is what we
should be concerned about here. Is a binary that initializes arrays in code
significantly larger?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18190