public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50052] [4.6/4.7/4.8 Regression] FAIL: gcc.dg/ipa/ipa-sra-2.c scan-tree-dump eipa_sra
Date: Mon, 26 Mar 2012 15:58:00 -0000 [thread overview]
Message-ID: <bug-50052-4-IIgVMGzqvx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50052-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50052
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #10 from Martin Jambor <jamborm at gcc dot gnu.org> 2012-03-26 15:53:11 UTC ---
The testcase is currently not being run on strict-alignment platforms
on the 4.6 and 4.7 branches and passes fine on trunk. Backporting the
misalignment expansion changes that allowed is not planned.
Thus, this PR can be finally closed as fixed. Thank you for your
patience.
prev parent reply other threads:[~2012-03-26 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 23:32 [Bug tree-optimization/50052] New: [4.6 " danglin at gcc dot gnu.org
2011-08-12 1:02 ` [Bug tree-optimization/50052] " danglin at gcc dot gnu.org
2011-08-12 7:41 ` [Bug tree-optimization/50052] [4.6/4.7 " rguenth at gcc dot gnu.org
2011-09-03 15:29 ` danglin at gcc dot gnu.org
2011-09-03 15:31 ` danglin at gcc dot gnu.org
2011-09-03 15:34 ` danglin at gcc dot gnu.org
2011-09-09 11:46 ` jamborm at gcc dot gnu.org
2011-09-30 9:46 ` ro at gcc dot gnu.org
2011-10-26 17:40 ` jakub at gcc dot gnu.org
2011-10-27 9:59 ` rguenth at gcc dot gnu.org
2012-03-01 14:46 ` jakub at gcc dot gnu.org
2012-03-26 15:55 ` [Bug tree-optimization/50052] [4.6/4.7/4.8 " jamborm at gcc dot gnu.org
2012-03-26 15:58 ` jamborm at gcc dot gnu.org [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-50052-4-IIgVMGzqvx@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).