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/26042] ICE in mark_reference_fields, at java/boehm.c:105 Date: Wed, 29 Mar 2006 15:12:00 -0000 [thread overview] Message-ID: <20060329151232.9966.qmail@sourceware.org> (raw) In-Reply-To: <bug-26042-602@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from tromey at gcc dot gnu dot org 2006-03-29 15:12 ------- The first time we lay out the type, we have the fields reversed. See parse.y:java_reorder_fields. I don't know why this happens. (We construct the field list in reverse order, presumably for efficiency. What is unclear is why the type can be laid out before the fields are correctly ordered.) In any case, on ppc32, the ordering of fields matters, because the class One can be packed more efficiently if 'b' comes first. Then what happens is that when we lay out Two$Three, the initial size of One is used to lay out the super class field. This field's size is not recomputed the second time we lay out Two$Three, yielding the incorrect result. One possible fix would be to reset the field sizes when we null out TYPE_SIZE in java_reorder_fields (and perhaps elsewhere). A better fix might be to remove the need for reordering fields. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26042
next prev parent reply other threads:[~2006-03-29 15:12 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-31 3:03 [Bug java/26042] New: " bje at gcc dot gnu dot org 2006-01-31 3:16 ` [Bug java/26042] " pinskia at gcc dot gnu dot org 2006-01-31 17:40 ` tromey at gcc dot gnu dot org 2006-02-03 4:06 ` bje at gcc dot gnu dot org 2006-02-04 2:29 ` tromey at gcc dot gnu dot org 2006-03-20 9:09 ` rguenth at gcc dot gnu dot org 2006-03-21 2:54 ` bje at gcc dot gnu dot org 2006-03-27 22:03 ` tromey at gcc dot gnu dot org 2006-03-28 1:14 ` tromey at gcc dot gnu dot org 2006-03-29 15:12 ` tromey at gcc dot gnu dot org [this message] 2006-03-29 16:52 ` tromey at gcc dot gnu dot org 2006-03-30 16:39 ` tromey at gcc dot gnu dot org 2006-03-30 16:47 ` tromey at gcc dot gnu dot org 2006-03-30 16:49 ` 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=20060329151232.9966.qmail@sourceware.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).