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 testsuite/54184] [4.8 Regression] gcc.dg/pr52558-1.c failure
Date: Mon, 06 Aug 2012 08:34:00 -0000 [thread overview]
Message-ID: <bug-54184-4-NpmkfpCZnJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54184-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54184
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-08-06
Component|middle-end |testsuite
CC| |aldyh at gcc dot gnu.org
Ever Confirmed|0 |1
Target Milestone|--- |4.8.0
--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-08-06 08:33:38 UTC ---
As said in the commit mail, the testcase is "broken". It scans for a random
string not in any way associated with what the testcase checks. That random
string no longer appears - instead of just deleting the scan I've opted to
let the author of the patch figure a better way to check for a successful
testcase.
Confirmed anyway.
next prev parent reply other threads:[~2012-08-06 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 23:57 [Bug middle-end/54184] New: " hjl.tools at gmail dot com
2012-08-06 8:34 ` rguenth at gcc dot gnu.org [this message]
2012-08-06 14:25 ` [Bug testsuite/54184] " hp at gcc dot gnu.org
2012-08-21 17:47 ` aldyh at gcc dot gnu.org
2012-09-02 16:36 ` danglin at gcc dot gnu.org
2012-09-05 21:16 ` aldyh at gcc dot gnu.org
2012-09-05 22:43 ` aldyh at gcc dot gnu.org
2012-09-06 8:54 ` rguenther at suse dot de
2012-09-06 17:06 ` dominiq at lps dot ens.fr
2012-09-07 16:00 ` aldyh at gcc dot gnu.org
2012-09-07 18:23 ` aldyh 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-54184-4-NpmkfpCZnJ@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).