public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52395] [4.7 Regression] Too conservative alignment info from SRA
Date: Mon, 27 Feb 2012 10:49:00 -0000 [thread overview]
Message-ID: <bug-52395-4-G4FXvO9hPB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52395-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52395
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|WAITING |NEW
Summary|[4.7 Regression] Alignment |[4.7 Regression] Too
|issue at O2 |conservative alignment info
| |from SRA
--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-27 10:48:37 UTC ---
Confirmed at least. The regression is because of a wrong-code fix.
next prev parent reply other threads:[~2012-02-27 10:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 7:50 [Bug tree-optimization/52395] New: [4.7 Regression] Alignment issue at O2 izamyatin at gmail dot com
2012-02-27 9:40 ` [Bug tree-optimization/52395] " rguenth at gcc dot gnu.org
2012-02-27 9:51 ` izamyatin at gmail dot com
2012-02-27 10:00 ` izamyatin at gmail dot com
2012-02-27 10:04 ` rguenth at gcc dot gnu.org
2012-02-27 10:06 ` rguenth at gcc dot gnu.org
2012-02-27 10:31 ` rguenth at gcc dot gnu.org
2012-02-27 10:49 ` rguenth at gcc dot gnu.org [this message]
2012-02-27 13:52 ` [Bug tree-optimization/52395] [4.7 Regression] Too conservative alignment info from SRA rguenth at gcc dot gnu.org
2012-02-27 14:55 ` rguenth at gcc dot gnu.org
2012-02-27 16:42 ` jamborm at gcc dot gnu.org
2012-02-27 17:19 ` jamborm at gcc dot gnu.org
2012-02-28 9:04 ` rguenther at suse dot de
2012-02-28 9:20 ` rguenth at gcc dot gnu.org
2012-02-28 9:29 ` 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-52395-4-G4FXvO9hPB@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).