public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57027] [4.9 Regression] ICE in gimple_assign_rhs_code, at gimple.h:2022
Date: Fri, 03 May 2013 10:11:00 -0000 [thread overview]
Message-ID: <bug-57027-4-Yr03elSK7v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57027-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57027
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #30004|0 |1
is obsolete| |
--- Comment #4 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2013-05-03 10:11:24 UTC ---
Created attachment 30016
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30016
amended patch
Using an i686-px-linux-gnu X hppa64-hp-hpux11.11 cross compiler, I've
verified that the previous patch fixes the gcc.c-torture/compile/991202-1.c
and gcc.dg/pr52132.c failures. The gcc.dg/pr41345.c compare-debug failure
happens independent of my code in convert_mult_to_fma.
I can't run the gcc.dg/torture/vec-cvt-1.c tests on my cross for lack of header
files.
The preprocessed testcase from the first attachment fails needs a different
sanity check in convert_mult_to_fma, which I have added in this amended patch.
next prev parent reply other threads:[~2013-05-03 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 23:26 [Bug translation/57027] New: " danglin at gcc dot gnu.org
2013-04-22 12:32 ` [Bug translation/57027] " rguenth at gcc dot gnu.org
2013-04-29 15:33 ` [Bug tree-optimization/57027] " danglin at gcc dot gnu.org
2013-05-02 15:42 ` danglin at gcc dot gnu.org
2013-05-02 16:28 ` amylaar at gcc dot gnu.org
2013-05-03 10:11 ` amylaar at gcc dot gnu.org [this message]
2013-05-03 10:53 ` rguenth at gcc dot gnu.org
2013-05-04 23:03 ` dave.anglin at bell dot net
2013-05-05 8:53 ` amylaar 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-57027-4-Yr03elSK7v@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).