public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jh@suse.cz,
	nobody@gcc.gnu.org, snyder@fnal.gov
Subject: Re: target/10213: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC
Date: Thu, 15 May 2003 04:41:00 -0000	[thread overview]
Message-ID: <20030515044154.13972.qmail@sources.redhat.com> (raw)

Synopsis: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC

State-Changed-From-To: analyzed->feedback
State-Changed-By: bangerth
State-Changed-When: Thu May 15 04:41:54 2003
State-Changed-Why:
    So, Scott, what's your verdict: should it be closed? What's
    the state on the 3.3 branch?
    
    Other question: if it's "fixed" by just disabling something
    (is this what you mean by "switching off") -- will we see
    the problem happening again if this code patch is switched
    on again by someone? Or was the code that produced the
    wrong code removed altogether? If this isn't the case, then
    I'd say we should keep the report, but lacking technical
    insight I leave this up to you.
    
    Thanks
      W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10213


             reply	other threads:[~2003-05-15  4:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  4:41 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-19 13:56 Jan Hubicka
2003-05-19 13:54 bangerth
2003-05-19  4:36 snyder
2003-05-18 18:46 Jan Hubicka
2003-05-15  1:06 snyder
2003-05-15  0:36 Dara Hazeghi
2003-03-26  8:31 steven

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=20030515044154.13972.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jh@suse.cz \
    --cc=nobody@gcc.gnu.org \
    --cc=snyder@fnal.gov \
    /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).