public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23286] missed fully redundant expression
Date: Tue, 16 Nov 2010 14:45:00 -0000	[thread overview]
Message-ID: <bug-23286-4-qAHSNIz4LN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-23286-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #31 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-16 14:39:50 UTC ---
(In reply to comment #29)
> I intended to work on this for GCC 4.6.  There are many vectorizer failures
> with the v3 patch. My local copy of the patch is at v6 :-)  I'll see if I can
> make some time to "forward-port" the differences between my v3 and v6 to
> Richi's updated patch.

I don't remember if you did send me your v6 privately (I at least can't find
it),
can you simply dump your most current variant here?

Thx.


       reply	other threads:[~2010-11-16 14:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23286-4@http.gcc.gnu.org/bugzilla/>
2010-11-16 14:45 ` rguenth at gcc dot gnu.org [this message]
2011-07-20  0:41 ` pinskia at gcc dot gnu.org
2011-07-29 20:15 ` pinskia at gcc dot gnu.org
2012-02-15 11:23 ` rguenth at gcc dot gnu.org
2012-02-15 16:07 ` rguenth at gcc dot gnu.org
2012-02-15 18:42 ` steven at gcc dot gnu.org
2012-02-16  9:48 ` rguenther at suse dot de
2012-02-16 12:58 ` rguenth at gcc dot gnu.org
2012-02-20 12:13 ` rguenth at gcc dot gnu.org
2012-02-23 14:00 ` aldot at gcc dot gnu.org
2021-08-21 21:55 ` [Bug tree-optimization/23286] Missed code hoisting optimization pinskia at gcc dot gnu.org
     [not found] <bug-23286-7849@http.gcc.gnu.org/bugzilla/>
2005-10-28 18:43 ` [Bug tree-optimization/23286] missed fully redundant expression pinskia at gcc dot gnu dot org
2007-10-10 22:59 ` steven at gcc dot gnu dot org
2007-10-16 13:33 ` steven at gcc dot gnu dot org
2007-10-26  4:09 ` astrange at ithinksw dot com
2008-02-23  5:23 ` pinskia at gcc dot gnu dot org
2008-11-21  6:43 ` steven at gcc dot gnu dot org
2008-11-23 13:09 ` steven at gcc dot gnu dot org
2008-11-23 13:12 ` steven at gcc dot gnu dot org
2008-11-23 13:24 ` steven at gcc dot gnu dot org
2008-11-23 13:33 ` rguenth at gcc dot gnu dot org
2008-11-23 13:45 ` rguenth at gcc dot gnu dot org
2008-11-23 14:22 ` steven at gcc dot gnu dot org
2008-11-23 18:31 ` dberlin at dberlin dot org
2008-11-27 15:27 ` steven at gcc dot gnu dot org
2008-12-01 22:02 ` steven at gcc dot gnu dot org
2009-08-04  9:06 ` steven at gcc dot gnu dot org
2010-01-17 12:34 ` rguenth at gcc dot gnu dot org
2010-01-17 12:35 ` rguenth at gcc dot gnu dot org
2010-01-17 12:56 ` rguenth at gcc dot gnu dot org
2010-01-17 13:00 ` steven at gcc dot gnu dot org
2010-02-24  9:40 ` steven at gcc dot gnu dot org
2005-08-08 17:46 [Bug tree-optimization/23286] New: " bonzini at gcc dot gnu dot org
2005-08-08 17:46 ` [Bug tree-optimization/23286] " bonzini at gcc dot gnu dot org
2005-08-08 18:42 ` pinskia at gcc dot gnu dot org
2005-08-08 18:53 ` dberlin at gcc dot gnu dot org
2005-08-08 18:56 ` dberlin at gcc dot gnu dot org
2005-08-08 19:34 ` pinskia at gcc dot gnu dot org
2005-08-08 19:36 ` pinskia at gcc dot gnu dot org
2005-08-08 19:54 ` pinskia at gcc dot gnu dot org
2005-08-08 20:29 ` dberlin at dberlin dot org
2005-08-08 20:40 ` dberlin at dberlin dot org
2005-08-29 12:35 ` pinskia 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=bug-23286-4-qAHSNIz4LN@http.gcc.gnu.org/bugzilla/ \
    --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).