public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6162: gcc 3.0.4: certain i386 asm reloader ice
Date: Thu, 24 Oct 2002 17:06:00 -0000	[thread overview]
Message-ID: <20021025000601.8862.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/6162; it has been noted by GNATS.

From: Kevin Ryde <user42@zip.com.au>
To: hubicka@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org
Subject: Re: optimization/6162: gcc 3.0.4: certain i386 asm reloader ice
Date: Fri, 25 Oct 2002 10:02:47 +1000

 hubicka@gcc.gnu.org writes:
 >
 > State-Changed-From-To: open->closed
 > State-Changed-Why:
 >     hubicka@kampanus:/aux/hubicka/3.2/egcs/build/gcc$ ./xgcc -B ./ -O ~/foo.c  -c
 
 Umm, no, that foo.c requires -fomit-frame-pointer in addition to -O to
 show the problem.  With that option it still occurs for me, using a
 build of today's cvs on my debian system.
 
 It also still occurs with the simpler bar.c I appended to the report
 (just "gcc -O -c bar.c" in that case).


             reply	other threads:[~2002-10-25  0:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 17:06 Kevin Ryde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01 13:46 Kevin Ryde
2002-10-31 10:26 Joe Buck
2002-10-30 15:06 Michael Matz
2002-10-30 14:56 Torbjorn Granlund
2002-10-30 14:46 Michael Matz
2002-10-30 14:26 Kevin Ryde
2002-10-30 14:16 Michael Matz
2002-10-30 13:36 Kevin Ryde
2002-10-30 12:36 Nathanael Nerode
2002-10-24 22:46 Andreas Jaeger
2002-10-24 22:39 aj
2002-10-10 11:06 hubicka
2002-08-02 16:06 Kevin Ryde
2002-04-03 16:26 Kevin Ryde

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=20021025000601.8862.qmail@sources.redhat.com \
    --to=user42@zip.com.au \
    --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).