public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/23300] New: DECL_FIELD_OFFSET == 0 versus build_field_ref Date: Tue, 09 Aug 2005 19:36:00 -0000 [thread overview] Message-ID: <20050809193000.23300.tromey@gcc.gnu.org> (raw) If I copy the current cvs classpath into the libjava build directory and try to build, I get an ICE. The problem occurs because of this code in build_field_ref: if (! flag_syntax_only && (flag_indirect_dispatch /* DECL_FIELD_OFFSET == 0 if we have no reference for the field, perhaps because we couldn't find the class in which the field is defined. FIXME: We should investigate this. */ || DECL_FIELD_OFFSET (field_decl) == 0)) ... flag_indirect_dispatch is false, but we have DECL_FIELD_OFFSET==0 for a 'this$0' field. So, we wind up using the indirect dispatch code anyway. This causes a later crash (we build a bogus tree since the otable is NULL). I haven't investigated why DECL_FIELD_OFFSET can be 0 here. -- Summary: DECL_FIELD_OFFSET == 0 versus build_field_ref Product: gcc Version: 4.1.0 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,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23300
next reply other threads:[~2005-08-09 19:36 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-09 19:36 tromey at gcc dot gnu dot org [this message] 2005-08-10 23:11 ` [Bug java/23300] " tromey at gcc dot gnu dot org 2005-08-10 23:22 ` pinskia at gcc dot gnu dot org 2005-08-11 1:58 ` pinskia at gcc dot gnu dot org 2005-08-11 2:01 ` pinskia at gcc dot gnu dot org 2005-08-11 2:39 ` pinskia at gcc dot gnu dot org 2005-08-11 2:59 ` pinskia at gcc dot gnu dot org 2005-08-11 3:06 ` pinskia at gcc dot gnu dot org 2005-08-11 3:37 ` pinskia at gcc dot gnu dot org 2005-08-11 11:38 ` rmathew at gcc dot gnu dot org 2005-08-15 19:38 ` tromey at gcc dot gnu dot org 2005-08-16 16:07 ` cvs-commit at gcc dot gnu dot org 2005-08-16 16:08 ` tromey 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=20050809193000.23300.tromey@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).