public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric.batut at allegorithmic dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54300] [4.7 Regression] Erroneous optimization causes wrong Neon data management
Date: Fri, 11 Jan 2013 10:42:00 -0000 [thread overview]
Message-ID: <bug-54300-4-fUD7Kbjc0U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54300-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54300
--- Comment #6 from Eric Batut <eric.batut at allegorithmic dot com> 2013-01-11 10:42:04 UTC ---
The patch by Christophe Lyon in the linked email was applied on trunk by Ramana
at rev 188951 (June 25th 2012), but gcc-trunk still fails as of today (rev
195102). The vswp instruction that causes d19 to be 0 before being used
afterwards is still generated.
Don't know about 4.7.x, though.
So unless my test is wrong (same command line and same test case as in the
original bug report), 4.8.0 should not be in the "Known to work" field. Did you
try with trunk ?
(In reply to comment #5)
> I could not reproduce this in a modified 4.7.0 which has patches from the
> trunk.
> I think it was fixed by http://gcc.gnu.org/ml/gcc-patches/2012-05/msg01732.html
> .
next prev parent reply other threads:[~2013-01-11 10:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 15:28 [Bug target/54300] New: [4.7/4.8 " eric.batut at allegorithmic dot com
2012-08-18 8:12 ` [Bug target/54300] " rguenth at gcc dot gnu.org
2012-08-20 16:11 ` eric.batut at allegorithmic dot com
2012-09-07 10:33 ` rguenth at gcc dot gnu.org
2012-09-20 10:26 ` jakub at gcc dot gnu.org
2012-10-25 12:56 ` eric.batut at allegorithmic dot com
2012-10-25 23:03 ` steven at gcc dot gnu.org
2012-12-03 15:42 ` rguenth at gcc dot gnu.org
2013-01-10 22:19 ` [Bug target/54300] [4.7 " pinskia at gcc dot gnu.org
2013-01-11 10:42 ` eric.batut at allegorithmic dot com [this message]
2013-04-11 8:00 ` rguenth at gcc dot gnu.org
2013-08-20 16:32 ` eric.batut at allegorithmic dot com
2013-10-04 17:29 ` [Bug rtl-optimization/54300] " rearnsha at gcc dot gnu.org
2013-10-08 9:36 ` [Bug rtl-optimization/54300] [4.7, 4.8, 4.9 Regression] regcprop incorrectly looks through parallel register swap operation ebotcazou at gcc dot gnu.org
2013-10-08 9:47 ` rearnsha at gcc dot gnu.org
2013-10-08 10:54 ` ebotcazou at gcc dot gnu.org
2013-11-20 13:55 ` rearnsha at gcc dot gnu.org
2013-12-05 9:56 ` [Bug rtl-optimization/54300] [4.7, 4.8 " steven at gcc dot gnu.org
2013-12-09 14:54 ` rearnsha at gcc dot gnu.org
2014-01-09 15:19 ` rearnsha at gcc dot gnu.org
2014-01-10 16:55 ` rearnsha at gcc dot gnu.org
2014-01-10 16:56 ` rearnsha at gcc dot gnu.org
2014-08-29 1:27 ` gregory.0xf0 at gmail dot com
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-54300-4-fUD7Kbjc0U@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).