[Bug libgcj/17021] libgcj verifier resolves classes too eagerly
mckinlay at redhat dot com
gcc-bugzilla@gcc.gnu.org
Tue Oct 25 20:36:00 GMT 2005
------- Comment #14 from mckinlay at redhat dot com 2005-10-25 20:36 -------
Robert, thanks very much for working on this. Examining the behaviour of Sun's
verifier a bit more shows that it does attempt to resolve classes where type
compatibility can not be proven by a simple string comparison, so I think that
your approach is correct.
I have one pedantic concern about the implementation of
_Jv_equalUtf8Const_classnames:
Say we're comparing a class called "Lfoo" and one called "fool", and fool is
given in the bytecode form while "Lfoo" is in the regular form. So,
_Jv_equalUtf8Const_classnames would end up comparing the strings "Lfoo" and
"Lfool;". Whats to stop it falsely returning true in this case?
Also, how about a more concise name for this function: _Jv_equalUtf8Classnames?
It will also need a ChangeLog entry, of course - other than these issues, this
patch looks pretty good.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17021
More information about the Java-prs
mailing list