public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/7611: Internal error while compiling libjava with -O Date: Fri, 16 Aug 2002 15:03:00 -0000 [thread overview] Message-ID: <20020816215601.4398.qmail@sources.redhat.com> (raw) The following reply was made to PR java/7611; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: Thomas Greve <tgreve@pc61.ixmid.com> Cc: gcc-gnats@gcc.gnu.org Subject: Re: java/7611: Internal error while compiling libjava with -O Date: 16 Aug 2002 15:55:43 -0600 >>>>> "Thomas" == Thomas Greve <tgreve@pc61.ixmid.com> writes: Thomas> java/io/FilePermission.java:153: internal error in generate_bytecode_insn - tree code not implemented: bit_field_ref The problem here is that gcc will sometimes change a field access into a bit-field access. This happens in the tree-simplification routines (offhand I forget exactly where, but I think there is another PR on this topic). The bytecode back end doesn't understand bit fields, and changing this would be difficult. I'm surprised to see this happen on x86. Previously I believe it was only a problem on the alpha. Try building without -O (the .class files are all that matter). That might help. I once started a patch to add a lang-hook to let `gcj -C' disable this particular optimization. I still have it lying around somewhere but I haven't found the time to test it on my alpha box yet :-( Tom
next reply other threads:[~2002-08-16 21:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-16 15:03 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-21 17:44 tromey 2002-08-16 4:48 Thomas Greve
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=20020816215601.4398.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).