public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aurelien at aurel32 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/66424] [5/6 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu in 32-bit mode
Date: Wed, 30 Sep 2015 14:44:00 -0000 [thread overview]
Message-ID: <bug-66424-4-OtuNTJkQ57@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66424-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66424
Aurelien Jarno <aurelien at aurel32 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aurelien at aurel32 dot net
--- Comment #11 from Aurelien Jarno <aurelien at aurel32 dot net> ---
For the record this bug badly affects the MIPS target when using
-mtune=mips32r2, option which is implied by the -march=mips32r2 option. This
causes for example ffmpeg to be miscompiled, which causes its testsuite to fail
completely.
It's not a problem anymore now that the bug has been fixed on the gcc-5-branch,
however I prefer to mention it here, so that people debugging this issue find
this bug.
prev parent reply other threads:[~2015-09-30 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 22:43 [Bug ipa/66424] New: " su at cs dot ucdavis.edu
2015-06-05 6:16 ` [Bug ipa/66424] " jakub at gcc dot gnu.org
2015-06-05 17:44 ` su at cs dot ucdavis.edu
2015-06-05 18:03 ` joseph at codesourcery dot com
2015-06-05 19:23 ` [Bug ipa/66424] [5/6 Regression] " jakub at gcc dot gnu.org
2015-06-22 12:03 ` rguenth at gcc dot gnu.org
2015-07-16 9:17 ` rguenth at gcc dot gnu.org
2015-07-21 19:55 ` vmakarov at gcc dot gnu.org
2015-09-29 16:38 ` vmakarov at gcc dot gnu.org
2015-09-29 18:26 ` doko at gcc dot gnu.org
2015-09-30 14:44 ` aurelien at aurel32 dot net [this message]
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-66424-4-OtuNTJkQ57@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).