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/17779] ICE: Seg fault
Date: Fri, 01 Oct 2004 17:58:00 -0000 [thread overview]
Message-ID: <20041001175832.7418.qmail@sourceware.org> (raw)
In-Reply-To: <20041001163537.17779.ericw@evcohs.com>
------- Additional Comments From tromey at gcc dot gnu dot org 2004-10-01 17:58 -------
I looked into this a little.
The bug is that we never call push_super_field() for the class
in question. In layout_class, push_super_field can be called,
but we fail this test and skip the call:
if (super_class && !CLASS_BEING_LAIDOUT (super_class))
In our case, CLASS_BEING_LAIDOUT (super_class) is true.
layout_class is only called once for the class in question,
so we never get another chance to call push_super_field.
Later we die because TYPE_FIELDS is NULL_TREE.
Offhand I'm not sure what to do.
Andrew has been working in this area lately, perhaps he
has an idea. I will ping him.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17779
next prev parent reply other threads:[~2004-10-01 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 16:35 [Bug java/17779] New: " ericw at evcohs dot com
2004-10-01 17:20 ` [Bug java/17779] " tromey at gcc dot gnu dot org
2004-10-01 17:32 ` pinskia at gcc dot gnu dot org
2004-10-01 17:52 ` ericw at evcohs dot com
2004-10-01 17:58 ` tromey at gcc dot gnu dot org [this message]
2004-10-04 8:52 ` aph at gcc dot gnu dot org
2004-10-05 14:47 ` pinskia at gcc dot gnu dot org
2004-10-05 14:55 ` cvs-commit at gcc dot gnu dot org
2004-10-05 15:51 ` pinskia at gcc dot gnu dot org
2004-10-05 16:04 ` ericw at evcohs dot com
2004-10-05 16:08 ` aph at redhat dot com
[not found] <bug-17779-6095@http.gcc.gnu.org/bugzilla/>
2008-01-04 11:07 ` aph at gcc dot gnu dot org
2008-01-04 15:06 ` dominiq at lps dot ens dot fr
2008-01-04 15:14 ` aph 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=20041001175832.7418.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: link
Be 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).