public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/54850] [4.8 Regression] FAIL: gcc.c-torture/execute/20041113-1.c execution, -Os
Date: Mon, 22 Oct 2012 15:50:00 -0000 [thread overview]
Message-ID: <bug-54850-4-vZEGRfN7cU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54850-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54850
--- Comment #11 from Pat Haugen <pthaugen at gcc dot gnu.org> 2012-10-22 15:50:06 UTC ---
(In reply to comment #9)
> Created attachment 28482 [details]
> Candidate patch.
>
> Could you both please test this patch?
The patch fixes the issue for me too, on both the reduced testcase and the full
benchmark.
next prev parent reply other threads:[~2012-10-22 15:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 19:27 [Bug middle-end/54850] New: " danglin at gcc dot gnu.org
2012-10-08 10:36 ` [Bug middle-end/54850] " rguenth at gcc dot gnu.org
2012-10-08 13:57 ` danglin at gcc dot gnu.org
2012-10-08 14:19 ` bernds at gcc dot gnu.org
2012-10-08 14:46 ` dave.anglin at bell dot net
2012-10-08 14:46 ` dave.anglin at bell dot net
2012-10-17 23:38 ` pthaugen at gcc dot gnu.org
2012-10-18 1:45 ` pthaugen at gcc dot gnu.org
2012-10-18 1:50 ` pthaugen at gcc dot gnu.org
2012-10-18 1:51 ` pthaugen at gcc dot gnu.org
2012-10-18 11:55 ` [Bug rtl-optimization/54850] " bernds at gcc dot gnu.org
2012-10-19 18:33 ` dave.anglin at bell dot net
2012-10-22 15:50 ` pthaugen at gcc dot gnu.org [this message]
2012-10-29 16:59 ` dje at gcc dot gnu.org
2012-11-08 17:11 ` bernds at gcc dot gnu.org
2012-11-16 0:12 ` pthaugen at gcc dot gnu.org
2012-11-23 12:08 ` bernds 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-54850-4-vZEGRfN7cU@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).