public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60029] [4.9 regression] FAIL: c-c++-common/dfp/convert-bfp.c -std=c++11 execution test Date: Mon, 10 Feb 2014 01:31:00 -0000 [thread overview] Message-ID: <bug-60029-4-G27horp8g3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60029-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60029 Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |amodra at gmail dot com Resolution|--- |DUPLICATE --- Comment #1 from Alan Modra <amodra at gmail dot com> --- Fixed by r207553. I'm not sure why this one didn't show up in the list of tests I reported fixed in http://gcc.gnu.org/ml/gcc-patches/2014-02/msg00273.html, and I've blown away that build directory. *** This bug has been marked as a duplicate of bug 60032 ***
prev parent reply other threads:[~2014-02-10 1:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-02 15:11 [Bug target/60029] New: " schwab@linux-m68k.org 2014-02-02 15:12 ` [Bug target/60029] " schwab@linux-m68k.org 2014-02-03 9:38 ` rguenth at gcc dot gnu.org 2014-02-10 1:31 ` amodra at gmail dot com [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-60029-4-G27horp8g3@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: linkBe 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).