public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5200: Store Motion is broken
Date: Mon, 18 Mar 2002 14:06:00 -0000	[thread overview]
Message-ID: <20020318220601.21980.qmail@sources.redhat.com> (raw)

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

From: Jakub Jelinek <jakub@redhat.com>
To: rodrigc@gcc.gnu.org, aj@suse.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/5200: Store Motion is broken
Date: Mon, 18 Mar 2002 17:03:31 -0500

 On Mon, Mar 18, 2002 at 09:41:50PM -0000, rodrigc@gcc.gnu.org wrote:
 >     Jakub, according to Andreas, this problem is
 >     fixed on the gcc 3.1 branch by your patch, but not on the mainline.
 >     
 >     Care to comment?
 
 On mainline IMHO it should be fixed the hard way, ie. apply the patch
 to fix store motion checks and then work out how to fix all store motion
 bugs.
 This is not possible for the branch, since when sm basically never worked
 in 3.1 development cycle, it would be actually a completely new feature
 coming in hard feature freeze.
 
 	Jakub


             reply	other threads:[~2002-03-18 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 14:06 Jakub Jelinek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 12:15 Andreas Jaeger
2003-05-12 12:00 Steven Bosscher
2003-01-01 21:36 Nathanael Nerode
2002-03-18 13:46 Andreas Jaeger
2002-03-18 13:41 rodrigc
2002-03-10 12:59 rodrigc
2001-12-26 20:06 aj

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=20020318220601.21980.qmail@sources.redhat.com \
    --to=jakub@redhat.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).