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/57380] [4.7/4.8/4.9 Regression] GCC 4.9.0 will not vectorize std::max and similar functions
Date: Thu, 23 May 2013 09:20:00 -0000	[thread overview]
Message-ID: <bug-57380-4-OlhNkEWtCD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57380-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
There was a deliberate change to require at least one invariant address or
a re-use of a previous load.

 2010-07-08  Richard Guenther  <rguenther@suse.de>

+       PR tree-optimization/44831
+       * tree-ssa-phiprop.c (phiprop_insert_phi): Properly build
+       a MEM_REF preserving TBAA info of the original dereference.
+       Dereference the original pointer if the address is not
+       invariant.
+       (propagate_with_phi): Fixup type checks wrt MEM_REFs.  Require
+       at least one invariant address that we are going to dereference.

I have a fix.


  parent reply	other threads:[~2013-05-23  9:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 21:42 [Bug tree-optimization/57380] New: " jewillco at osl dot iu.edu
2013-05-22 21:47 ` [Bug tree-optimization/57380] " jewillco at osl dot iu.edu
2013-05-23  8:35 ` [Bug tree-optimization/57380] [4.7/4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-05-23  9:20 ` rguenth at gcc dot gnu.org [this message]
2013-05-23 12:24 ` [Bug tree-optimization/57380] [4.7/4.8 " rguenth at gcc dot gnu.org
2013-10-30 12:23 ` rguenth at gcc dot gnu.org
2014-01-16 21:04 ` law at redhat dot com
2014-01-16 21:04 ` law at redhat dot com
2014-06-30  2:01 ` pinskia at gcc dot gnu.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-57380-4-OlhNkEWtCD@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).