public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55325] New: [4.8 Regression]: g++.dg/cpp0x/constexpr-complex.C excess errors
Date: Wed, 14 Nov 2012 16:10:00 -0000 [thread overview]
Message-ID: <bug-55325-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55325
Bug #: 55325
Summary: [4.8 Regression]: g++.dg/cpp0x/constexpr-complex.C
excess errors
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hp@gcc.gnu.org
CC: emsr@gcc.gnu.org
Host: x86_64-unknown-linux-gnu
Target: cris-axis-elf, sh4-linux, i686-linux, x86_64-linux
This test previously passed, now it fails.
A patch in the revision range (last_known_working:first_known_failing)
193374:193385
exposed or caused this regression. Since then it fails as follows:
Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/dg.exp ...
...
FAIL: g++.dg/cpp0x/constexpr-complex.C (test for excess errors)
In g++.log for cris-elf:
Executing on host:
/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/g++/../../g++
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/g++/../../
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/cpp0x/constexpr-complex.C
-fno-diagnostics-show-caret -nostdinc++
-I/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/libstdc++-v3/include/cris-elf
-I/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/libstdc++-v3/include
-I/tmp/hpautotest-gcc1/gcc/libstdc++-v3/libsupc++
-I/tmp/hpautotest-gcc1/gcc/libstdc++-v3/include/backward
-I/tmp/hpautotest-gcc1/gcc/libstdc++-v3/testsuite/util -fmessage-length=0
-std=c++0x -S -isystem
/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/targ-include -isystem
/tmp/hpautotest-gcc1/gcc/newlib/libc/include -o constexpr-complex.s
(timeout = 300)
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/cpp0x/constexpr-complex.C: In
constructor 'constexpr complex::complex(float, float)':
/tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/cpp0x/constexpr-complex.C:12:26:
error: unable to find numeric literal operator 'operator"" fi'
Looks like the regression is universal:
sh4-linux: <http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01164.html>
i686-linux: <http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01171.html>
x86_64-linux: <http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg01173.html>
Author of suspect patch in revision range CC:ed.
next reply other threads:[~2012-11-14 16:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 16:10 hp at gcc dot gnu.org [this message]
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
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@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).