public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51876] [4.7 regression] Recent extra neon related testsuite regressions on arm-linux-gnueabi
Date: Tue, 17 Jan 2012 12:15:00 -0000 [thread overview]
Message-ID: <bug-51876-4-3n9Ls0SBU3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51876-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51876
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-01-17 11:59:23 UTC ---
Created attachment 26349
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26349
gcc47-pr51876.patch
Untested fix (well, tested that the ICEs are gone on all these tests with a
cross). vswp just seems to swap two vector registers, so it doesn't matter
which one is the first and which is the second, and the pattern only has two
operands, not 3.
Ramana, could you please bootstrap/regtest it on some real hw?
next prev parent reply other threads:[~2012-01-17 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 1:31 [Bug target/51876] New: " ramana at gcc dot gnu.org
2012-01-17 1:36 ` [Bug target/51876] " ramana at gcc dot gnu.org
2012-01-17 10:19 ` rguenth at gcc dot gnu.org
2012-01-17 12:15 ` jakub at gcc dot gnu.org [this message]
2012-01-17 13:59 ` ramana at gcc dot gnu.org
2012-01-19 13:00 ` rguenth at gcc dot gnu.org
2012-01-19 13:26 ` jakub at gcc dot gnu.org
2012-01-19 16:09 ` ramana at gcc dot gnu.org
2012-01-19 17:14 ` jakub at gcc dot gnu.org
2012-01-19 18:05 ` jakub 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-51876-4-3n9Ls0SBU3@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).