public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "andreast at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/23597] New: Can not compile current classpath with gcj (AbstractDocument.java) Date: Sat, 27 Aug 2005 20:32:00 -0000 [thread overview] Message-ID: <20050827203238.23597.andreast@gcc.gnu.org> (raw) Gcj bails out in compiling current classpath. Also running mauve test fails: gnu/testlet/javax/swing/text/ElementIterator/ElementIteratorTest.java:87: error: Type 'ElementIterator' not found in the declaration of the local variable 'iter'. ElementIterator iter = new ElementIterator(doc); ^ 1 error Building classpath with jikes succeeds, so I guess it's gcj issue. This patch (http://lists.gnu.org/archive/html/classpath-patches/2005-08/msg00447.html) fixes compilation of classpath, but according to the experts the AbstractDocument.java code is correct. So the patch works around a gcj issue. The sooner or later this bug will appear in gcc, means as soon as a new classpath import has been done. To reproduce, pick classpath cvs and build with a current gcc tree. -- Summary: Can not compile current classpath with gcj (AbstractDocument.java) Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: andreast at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org GCC build triplet: powerpc-apple-darwin8.2.0 GCC host triplet: powerpc-apple-darwin8.2.0 GCC target triplet: powerpc-apple-darwin8.2.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23597
next reply other threads:[~2005-08-27 20:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-27 20:32 andreast at gcc dot gnu dot org [this message] 2005-08-27 20:36 ` [Bug java/23597] " pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050827203238.23597.andreast@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).