public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60766] [4.8/4.9 Regression] Wrong optimization with -O2
Date: Sun, 06 Apr 2014 12:44:00 -0000 [thread overview]
Message-ID: <bug-60766-4-YoPYf5147x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60766-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60766
Mikael Pettersson <mikpelinux at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpelinux at gmail dot com
--- Comment #4 from Mikael Pettersson <mikpelinux at gmail dot com> ---
Created attachment 32552
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32552&action=edit
self-contained test case, compilable as C and C++
The wrong-code reproduces for me with gcc 4.7 and 4.8 on x86_64-linux. For
trunk it was fixed by r204515, which doesn't appear to be a wrong-code fix.
Backporting r204515 to 4.8 fixes the wrong-code there too, but I haven't tested
it beyond this test case.
next prev parent reply other threads:[~2014-04-06 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-60766-4@http.gcc.gnu.org/bugzilla/>
2014-04-05 0:05 ` pinskia at gcc dot gnu.org
2014-04-05 8:04 ` Joost.VandeVondele at mat dot ethz.ch
2014-04-06 8:20 ` netheril96 at gmail dot com
2014-04-06 12:44 ` mikpelinux at gmail dot com [this message]
2014-04-07 10:26 ` [Bug tree-optimization/60766] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-04-07 14:04 ` rguenth at gcc dot gnu.org
2014-04-07 14:10 ` [Bug tree-optimization/60766] [4.7/4.8 " rguenth at gcc dot gnu.org
2014-05-06 9:02 ` rguenth at gcc dot gnu.org
2014-05-06 9:03 ` [Bug tree-optimization/60766] [4.7 " rguenth at gcc dot gnu.org
2014-06-12 13:38 ` rguenth 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-60766-4-YoPYf5147x@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).