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/58228] [4.7 Regression] wrong code (with vectorization?) at -O3 on x86_64-linux-gnu
Date: Fri, 23 May 2014 09:46:00 -0000 [thread overview]
Message-ID: <bug-58228-4-svGj67uxXP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58228-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58228
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri May 23 09:46:18 2014
New Revision: 210847
URL: http://gcc.gnu.org/viewcvs?rev=210847&root=gcc&view=rev
Log:
2014-05-23 Richard Biener <rguenther@suse.de>
Backport from mainline
2013-08-30 Richard Biener <rguenther@suse.de>
PR tree-optimization/58228
* tree-vect-data-refs.c (vect_analyze_data_ref_access): Do not
allow invariant loads in nested loop vectorization.
* gcc.dg/torture/pr58228.c: New testcase.
2013-09-26 Richard Biener <rguenther@suse.de>
PR tree-optimization/58539
* tree-vect-loop.c (vect_create_epilog_for_reduction): Honor
the fact that debug statements are not taking part in loop-closed
SSA construction.
* gcc.dg/torture/pr58539.c: New testcase.
Added:
branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr58228.c
branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr58539.c
Modified:
branches/gcc-4_7-branch/gcc/ChangeLog
branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
branches/gcc-4_7-branch/gcc/tree-vect-data-refs.c
branches/gcc-4_7-branch/gcc/tree-vect-loop.c
next prev parent reply other threads:[~2014-05-23 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 7:56 [Bug tree-optimization/58228] New: " su at cs dot ucdavis.edu
2013-08-23 8:06 ` [Bug tree-optimization/58228] [4.7/4.8/4.9 Regression] " mpolacek at gcc dot gnu.org
2013-08-23 9:28 ` jakub at gcc dot gnu.org
2013-08-28 20:52 ` jakub at gcc dot gnu.org
2013-08-29 11:01 ` rguenth at gcc dot gnu.org
2013-08-30 7:49 ` rguenth at gcc dot gnu.org
2013-08-30 7:53 ` [Bug tree-optimization/58228] [4.7/4.8 " rguenth at gcc dot gnu.org
2013-09-03 12:16 ` rguenth at gcc dot gnu.org
2014-05-23 9:46 ` rguenth at gcc dot gnu.org [this message]
2014-05-23 9:46 ` [Bug tree-optimization/58228] [4.7 " rguenth 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-58228-4-svGj67uxXP@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).