public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/26135] store copyprop not effective
Date: Mon, 06 Feb 2006 17:36:00 -0000	[thread overview]
Message-ID: <20060206173640.6265.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26135-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rguenth at gcc dot gnu dot org  2006-02-06 17:36 -------
And I have a patch.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dnovillo at redhat dot com
         AssignedTo|unassigned at gcc dot gnu   |rguenth at gcc dot gnu dot
                   |dot org                     |org
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-02-06 17:36:39
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26135


  reply	other threads:[~2006-02-06 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 17:36 [Bug tree-optimization/26135] New: " rguenth at gcc dot gnu dot org
2006-02-06 17:36 ` rguenth at gcc dot gnu dot org [this message]
2006-02-07 15:46 ` [Bug tree-optimization/26135] " rguenth at gcc dot gnu dot org
2006-02-07 16:35 ` steven at gcc dot gnu dot org
2006-02-08 13:18 ` rguenth at gcc dot gnu dot org
2006-04-07  8:04 ` rguenth at gcc dot gnu dot org
2006-04-07  8:05 ` rguenth at gcc dot gnu dot org

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=20060206173640.6265.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).