-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jess,
On 3/12/2011 11:16 AM, Jess Holle wrote: > Clearly there's normally extra expense for debug/smap information, > though it's not clear to me whether this works against the 65K limit or > not. SMAP information is stored separately from the code, so it doesn't count against the 65K per-method limit. There appears to be a 2^32 - 6 limit for the length of the SMAP debug extension attribute, though. > Note the last 2 results are essentially identical (I didn't compare byte > counts). What about disabling SMAP generation in the other cases? > Yet when I try this last configuration with the JSP that goes over 65K > it fails with JDT and succeeds with javac. So it's the Java compiler that fails, not the JSP compiler? That is, JSP - -> Java looks fine, but Java -> bytecode fails? I'm still surprised that the Java methods are even on the brink of exceeding the 65K method limit. If it's the Java compiler failing, then it could be that javac just generates tighter bytecode than JDT. If it's the difference between 65530 and 65536 bytes, then one will succeed while the other one fails. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1+WR8ACgkQ9CaO5/Lv0PDq0wCeNRnPfbW3Tywo5FcAdC4Fqcsp t2AAn0M4llRHGfraSaZZAgqIU6mU8ezV =CcIX -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
