public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65787] [5 Regression] Miscompile due to bad vector swap optimization for little endian
Date: Sun, 19 Apr 2015 16:53:00 -0000 [thread overview]
Message-ID: <bug-65787-4-LqV6YJMraU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65787-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65787
--- Comment #11 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Author: wschmidt
Date: Sun Apr 19 16:53:22 2015
New Revision: 222222
URL: https://gcc.gnu.org/viewcvs?rev=222222&root=gcc&view=rev
Log:
[gcc]
2015-04-18 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Jakub Jelinek <jakub@redhat.com>
Backport from mainline r222205
2015-04-17 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Jakub Jelinek <jakub@redhat.com>
PR target/65787
* config/rs6000/rs6000.c (rtx_is_swappable_p): Ensure that a
subsequent SH_NONE operand does not overwrite an existing *special
value.
(adjust_extract): Handle case where a vec_extract operation is
wrapped in a PARALLEL.
[gcc/testsuite]
2015-04-18 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Backport from mainline r222205
2015-04-17 Bill Schmidt <wschmidt@linux.vnet.ibm.com>
PR target/65787
* gcc.target/powerpc/pr65787.c: New.
Added:
branches/gcc-4_8-branch/gcc/testsuite/gcc.target/powerpc/pr65787.c
Modified:
branches/gcc-4_8-branch/gcc/ChangeLog
branches/gcc-4_8-branch/gcc/config/rs6000/rs6000.c
branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-04-19 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 19:49 [Bug target/65787] New: [5.1 regression] " wschmidt at gcc dot gnu.org
2015-04-16 19:50 ` [Bug target/65787] " wschmidt at gcc dot gnu.org
2015-04-16 20:06 ` wschmidt at gcc dot gnu.org
2015-04-16 20:08 ` [Bug target/65787] [5 Regression] " jakub at gcc dot gnu.org
2015-04-16 21:51 ` jakub at gcc dot gnu.org
2015-04-16 21:58 ` jakub at gcc dot gnu.org
2015-04-17 4:46 ` wschmidt at gcc dot gnu.org
2015-04-17 13:28 ` wschmidt at gcc dot gnu.org
2015-04-17 14:51 ` wschmidt at gcc dot gnu.org
2015-04-17 15:09 ` wschmidt at gcc dot gnu.org
2015-04-17 20:36 ` wschmidt at gcc dot gnu.org
2015-04-17 22:05 ` wschmidt at gcc dot gnu.org
2015-04-19 16:51 ` wschmidt at gcc dot gnu.org
2015-04-19 16:53 ` wschmidt at gcc dot gnu.org [this message]
2015-04-19 16:55 ` wschmidt 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-65787-4-LqV6YJMraU@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).