public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47228] [4.6 Regression] wrong code with loop
Date: Wed, 26 Jan 2011 00:17:00 -0000 [thread overview]
Message-ID: <bug-47228-4-isvlwclpBP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47228-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47228
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|i686-pc-linux-gnu |i?86-pc-linux-gnu
Status|UNCONFIRMED |NEW
Keywords| |wrong-code
Last reconfirmed| |2011.01.26 00:09:23
Component|c |tree-optimization
Host|i686-pc-linux-gnu |
Ever Confirmed|0 |1
Summary|likely improper segfault in |[4.6 Regression] wrong code
|generated code |with loop
Target Milestone|--- |4.6.0
Build|i686-pc-linux-gnu |
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-01-26 00:09:23 UTC ---
Confirmed, fails also with -O2 -fno-inline (or marking func_2 as
noinline/noclone).
This is rather weird, the correct code (at the tree level even) is produced
with -m64.
next prev parent reply other threads:[~2011-01-26 0:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 23:05 [Bug c/47228] New: likely improper segfault in generated code LpSolit at netscape dot net
2011-01-26 0:17 ` pinskia at gcc dot gnu.org [this message]
2011-01-26 9:50 ` [Bug tree-optimization/47228] [4.6 Regression] wrong code with loop jakub at gcc dot gnu.org
2011-01-26 9:50 ` jakub at gcc dot gnu.org
2011-01-26 9:53 ` jakub at gcc dot gnu.org
2011-01-26 19:58 ` jamborm at gcc dot gnu.org
2011-01-26 21:14 ` jamborm at gcc dot gnu.org
2011-01-27 14:10 ` jamborm at gcc dot gnu.org
2011-01-27 14:26 ` jamborm at gcc dot gnu.org
2011-02-02 18:16 ` dnovillo 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-47228-4-isvlwclpBP@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).