public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Christoph Breitkopf <chr.breitkopf@magrathea.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/3480: gcc-3.0, bad code generated with -O3  -fomit-frame-pointer on intel x86
Date: Mon, 03 Dec 2001 04:06:00 -0000	[thread overview]
Message-ID: <20011203120603.806.qmail@sources.redhat.com> (raw)

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

From: Christoph Breitkopf <chr.breitkopf@magrathea.de>
To: rodrigc@gcc.gnu.org
Cc:  
Subject: Re: optimization/3480: gcc-3.0, bad code generated with -O3 
 -fomit-frame-pointer on intel x86
Date: Mon, 03 Dec 2001 12:40:43 +0100

 rodrigc@gcc.gnu.org schrieb:
 > 
 > Synopsis: gcc-3.0, bad code generated with -O3 -fomit-frame-pointer on intel x86
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: rodrigc
 > State-Changed-When: Sat Dec  1 22:49:12 2001
 > State-Changed-Why:
 >     I think this has been fixed by:
 >     http://gcc.gnu.org/ml/gcc-patches/2001-11/msg00698.html
 > 
 >     Can you try a gcc 3.0.3 snapshot and verify this?
 
 I tried with gcc 3.1 20011126 (experimental),
 and yes, the SEGV with -fomit-frame-pointer has been fixed!
 
 Thanks for the good work.
 
 Regards,
 Chris


             reply	other threads:[~2001-12-03 12:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  4:06 Christoph Breitkopf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-11 22:26 rodrigc
2001-12-11 22:22 rodrigc
2001-12-03  4:36 Juergen Keil
2001-12-03  4:36 Juergen Keil
2001-12-01 22:56 rodrigc
2001-12-01 22:49 rodrigc

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=20011203120603.806.qmail@sources.redhat.com \
    --to=chr.breitkopf@magrathea.de \
    --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).