This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug java/12768] New: gcj can no longer compile classpath
- From: "tromey at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 24 Oct 2003 20:57:48 -0000
- Subject: [Bug java/12768] New: gcj can no longer compile classpath
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12768
Summary: gcj can no longer compile classpath
Product: gcc
Version: 3.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tromey at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
With the addition of the "signers" field to Class, gcj
can no longer compile Classpath. This happens because
Classpath's Class has its own "signers" field, and gcj
gets confused by the existence of two fields.
Ideally, when compiling to bytecode, gcj would ignore
its internal fields on Class and Object. This would let
us continue to build Classpath.
3.3 was able to compile Classpath.