From: Jeffrey A Law <law@cygnus.com>
To: Craig Burley <burley@gnu.org>
Cc: egcs@cygnus.com
Subject: Re: egcs snapshot crash with -O6 -- 970125-0.f (ADDRESSOF?)
Date: Tue, 05 May 1998 23:20:00 -0000 [thread overview]
Message-ID: <4304.894433282@hurl.cygnus.com> (raw)
In-Reply-To: <199804181219.IAA22645@melange.gnu.org>
In message <199804181219.IAA22645@melange.gnu.org>you write:
> Here's a little test case I've got that crashes egcs (and gcc 2.8.1)
> in the 980328 snapshot, but not 1.0.1:
I see it's already in the testsuite. Good :-)
> I debugged just enough in the gcc 2.8.1 base to discover that
> an ADDR_EXPR(ADDR_EXPR(VAR_DECL)) was causing a crash in, IIRC,
> expand_expr, because an rtx ended up being an "addressof", which
> was not accounted for in the switch statement. (Is this the
> ADDRESSOF stuff people have talked about?)
Yup.
jeff
prev parent reply other threads:[~1998-05-05 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-18 8:18 Craig Burley
1998-05-05 23:20 ` Jeffrey A Law [this message]
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=4304.894433282@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=burley@gnu.org \
--cc=egcs@cygnus.com \
/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).