public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roger Sayle <roger@eyesopen.com>
To: <gcc@gcc.gnu.org>
Cc: Mark Mitchell <mark@codesourcery.com>,
	"David S. Miller" <davem@redhat.com>, Andreas Jaeger <aj@suse.de>,
	Daniel Berlin <dberlin@dberlin.org>,
	Richard Henderson <rth@redhat.com>
Subject: Re: GCSE store motion
Date: Wed, 15 May 2002 09:07:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0205150912060.22497-100000@www.eyesopen.com> (raw)


I'm more than happy to attempt to fix GCSE store motion, but my current
understanding is that its working perfectly!

PR opt/5200 was filed by Andreas Jaeger on the supporting evidence of
PR opt/5172 and postings by Dan Berlin to gcc-patches last year.

In the review of my patch to that attempted to fix PR/5172
http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01142.html, it
became clear that it was glibc at fault and not the store motion
pass at all.

Hence the only remaining claims that store motion is broken are
the comments by Dan Berlin, but as far as I am aware there are
no known examples of failing test cases.  Dan also claimed that
store motion wasn't currently doing anything, but clearly PR/5172
showed that duplicate stores are being eliminated in real code.

To appease the paranoia of the pending GCC 3.1 release it was
decided to disable this optimization even without conclusive
evidence that anything was broken.  Unless a failing test in
the GCC test suite starts passing, I'm against disabling a
functional optimization on the CVS mainline.  Finding a failing
test case would also help the call for volunteers to fix it.

Roger
--
Roger Sayle,                         E-mail: roger@eyesopen.com
OpenEye Scientific Software,         WWW: http://www.eyesopen.com/
Suite 1107, 3600 Cerrillos Road,     Tel: (+1) 505-473-7385
Santa Fe, New Mexico, 87507.         Fax: (+1) 505-473-0833

             reply	other threads:[~2002-05-15 15:42 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  9:07 Roger Sayle [this message]
2002-05-15  9:21 ` Daniel Berlin
2002-05-15  9:53   ` Daniel Berlin
2002-05-15 10:05     ` Roger Sayle
2002-05-15 10:09       ` Daniel Berlin
2002-05-15 10:21         ` Jakub Jelinek
2002-05-15 10:31           ` Mark Mitchell
2002-05-15 11:56         ` law
2002-05-15 11:05     ` Kevin Handy
2002-05-15 11:50       ` Janis Johnson
2002-05-15 11:54     ` law
2002-05-15  9:58   ` Roger Sayle
2002-05-15 10:06     ` Daniel Berlin
2002-05-15 10:15       ` David Edelsohn
2002-05-15 11:56         ` law
2002-05-15 12:07           ` Mark Mitchell
2002-05-15 10:18       ` Roger Sayle
2002-05-15 10:32         ` David Edelsohn
2002-05-16  1:51       ` Jan Hubicka
2002-05-16  9:59         ` Daniel Berlin
2002-05-15 10:02   ` Mark Mitchell
2002-05-15 10:08     ` Roger Sayle
2002-05-15 10:14       ` Mark Mitchell
2002-05-15 10:41         ` Roger Sayle
2002-05-15 11:56         ` law
2002-05-15 12:07           ` Mark Mitchell
2002-05-15 13:48             ` Toon Moene
2002-05-16 13:50               ` law
2002-05-17 15:03               ` Tim Hollebeek
2002-05-16 13:53             ` law
2002-05-16 14:44               ` Daniel Berlin
2002-05-16 21:12                 ` Eric Christopher
2002-05-15 12:32   ` law
     [not found] <20020516114838.949B6F28C9@nile.gnat.com.suse.lists.egcs>
     [not found] ` <164620000.1021559673@gandalf.codesourcery.com.suse.lists.egcs>
2002-05-16 11:42   ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2002-05-16  8:29 Robert Dewar
2002-05-16  5:36 Robert Dewar
2002-05-16  5:30 Robert Dewar
2002-05-16  7:59 ` Mark Mitchell
2002-05-16  8:31 ` Daniel Berlin
2002-05-15 13:56 Robert Dewar
2002-05-15 14:06 ` Gabriel Dos Reis
2002-05-15 15:09 ` Toon Moene
2002-05-15 15:20 ` Dale Johannesen
2002-05-15 12:45 Robert Dewar
2002-05-15 12:56 ` Mark Mitchell
2002-05-15 13:29 ` Daniel Berlin
2002-05-14 23:27 David S. Miller
2002-05-14 23:33 ` Daniel Berlin
2002-05-15  0:03   ` David S. Miller
2002-05-15  0:41     ` Daniel Berlin
2002-05-15  1:27     ` Jan Hubicka
2002-05-15  1:22 ` Mark Mitchell
2002-05-15  1:29   ` David S. Miller
2002-05-15  1:32     ` Mark Mitchell

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=Pine.LNX.4.33.0205150912060.22497-100000@www.eyesopen.com \
    --to=roger@eyesopen.com \
    --cc=aj@suse.de \
    --cc=davem@redhat.com \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=rth@redhat.com \
    /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).