From the Classpath mailing list: http://mail.gnu.org/pipermail/classpath/2002-February/001909.html This front-end bug in emitted class files, if fixed, will expose bugs in backend jits the same way classes compiled by JDK 1.4 or jikes 1.15a will. Release: 3.0.4 Environment: cygwin
Fix: When emitting a qualified field or method reference, JLS 13 requires that the compiler link the reference to the type of the qualifying expression; even if that class only inherits the field or method.
Hello, could you please report whether this bug still occurs with current versions of gcc (ie 3.3)? The message referenced by this bug is not longer available, so if a working link to that could be provided, that would be great too. As always, testcases make it much easier to verify whether bugs are still present. Thanks, Dara
Found the email: <http://mail.gnu.org/archive/html/classpath/2002-02/msg00112.html>. From that email: It makes a difference in this example: in A.java: class A { static void m() { System.out.print("a"); } } in B.java: class B extends A {} in C.java: class C { public static void main(String[] args) { B.m(); } } Now, recompile B.java: class B extends A { static void m() { System.out.print("b"); } } The result of executing the (unchanged) C.class should now be "b", not "a".
Forgot to menation that I could reproduce the bug on the mainline (20030823).
All gcj front end bugs have been fixed by the gcj-eclipse branch merge. I'm mass-closing the affected PRs. If you believe one of these was closed in error, please reopen it with a note explaining why. Thanks.