public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/55325] [4.8 Regression]: g++.dg/cpp0x/constexpr-complex.C excess errors Date: Wed, 14 Nov 2012 22:28:00 -0000 [thread overview] Message-ID: <bug-55325-4-QHSfPdoBrn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55325-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55325 --- Comment #8 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-11-14 22:28:19 UTC --- The latter seems indeed a target issue, as you can read here Hans-Peter reported it for cris-elf, but have a look to the testresults mailing list to double check. Personally, I would recommend applying asap the (obvious, IMHO) fixes for the first two regression to remove noise from the results of, eg, people testing on Linux.
next prev parent reply other threads:[~2012-11-14 22:28 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-14 16:10 [Bug c++/55325] New: " hp at gcc dot gnu.org 2012-11-14 16:18 ` [Bug c++/55325] " paolo.carlini at oracle dot com 2012-11-14 16:20 ` paolo.carlini at oracle dot com 2012-11-14 16:59 ` hp at gcc dot gnu.org 2012-11-14 20:21 ` 3dw4rd at verizon dot net 2012-11-14 20:37 ` paolo.carlini at oracle dot com 2012-11-14 21:52 ` 3dw4rd at verizon dot net 2012-11-14 22:18 ` 3dw4rd at verizon dot net 2012-11-14 22:28 ` paolo.carlini at oracle dot com [this message] 2012-11-14 22:31 ` paolo.carlini at oracle dot com 2012-11-14 22:43 ` ubizjak at gmail dot com 2012-11-15 2:40 ` hp at gcc dot gnu.org 2012-11-15 2:57 ` jason at gcc dot gnu.org 2012-11-15 8:26 ` ubizjak at gmail dot com 2012-11-15 8:44 ` hp at gcc dot gnu.org 2012-11-15 16:24 ` ubizjak at gmail dot com 2012-11-15 20:06 ` hp 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-55325-4-QHSfPdoBrn@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).