public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: George Garvey <tmwg@inxservices.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6396: 3.1 flow.c 583 ICE with -frename-registers
Date: Thu, 25 Apr 2002 10:36:00 -0000 [thread overview]
Message-ID: <20020425173602.30062.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/6396; it has been noted by GNATS.
From: George Garvey <tmwg@inxservices.com>
To: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/6396: 3.1 flow.c 583 ICE with -frename-registers
Date: Thu, 25 Apr 2002 10:26:15 -0700
You are right. I messed something up in the makefile, and added -O0
by mistake after -O2 et al. I just verified that removing the -O0 and only
using -O2 and the other options does not get an ICE, the file compiles
successfully.
On Thu, Apr 25, 2002 at 04:35:08PM -0000, jakub@gcc.gnu.org wrote:
> Synopsis: 3.1 flow.c 583 ICE with -frename-registers
>
> State-Changed-From-To: open->analyzed
> State-Changed-By: jakub
> State-Changed-When: Thu Apr 25 09:35:06 2002
> State-Changed-Why:
> Using -frename-registers at -O0 is a bad idea.
> I've just submitted a patch which does register renaming
> only when optimizing.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6396
next reply other threads:[~2002-04-25 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 10:36 George Garvey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 4:14 reichelt
2002-04-25 9:35 jakub
2002-04-21 11:56 c++/6396: 3.1 flow.c:583 " tmwg-gcc
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=20020425173602.30062.qmail@sources.redhat.com \
--to=tmwg@inxservices.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: 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).