public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail 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:43:00 -0000 [thread overview]
Message-ID: <bug-55325-4-D4rU3tLJYh@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 #10 from Uros Bizjak <ubizjak at gmail dot com> 2012-11-14 22:42:45 UTC ---
(In reply to comment #7)
> > Right, thanks, I was just about to analyze that one. Speaking of that commit,
> > some of the new tests fail for me:
> > FAIL: g++.dg/cpp0x/gnu_fext-numeric-literals.C (test for excess errors)
> > FAIL: g++.dg/cpp0x/std_fext-numeric-literals.C (test for excess errors)
> >
> > and in g++.log:
> > Excess errors:
> > /tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/cpp0x/gnu_fext-numeric-literals.C:94:3:
> > ...
> > maybe related, maybe material for a new PR.
>
> I'm not getting this on x86_64-linux at least. What target are you on?
Probably due to the fact that x86_64 defines TARGET_C_MODE_FOR_SUFFIX that
declares support for non-standard 'q' and 'w' suffixes. There is a small group
of targets that declare this define:
config/aarch64/aarch64.c:#undef TARGET_C_MODE_FOR_SUFFIX
config/aarch64/aarch64.c:#define TARGET_C_MODE_FOR_SUFFIX
aarch64_c_mode_for_suffix
config/ia64/ia64.c:#undef TARGET_C_MODE_FOR_SUFFIX
config/ia64/ia64.c:#define TARGET_C_MODE_FOR_SUFFIX ia64_c_mode_for_suffix
config/i386/i386.c.orig:#undef TARGET_C_MODE_FOR_SUFFIX
config/i386/i386.c.orig:#define TARGET_C_MODE_FOR_SUFFIX ix86_c_mode_for_suffix
config/i386/i386.c:#undef TARGET_C_MODE_FOR_SUFFIX
config/i386/i386.c:#define TARGET_C_MODE_FOR_SUFFIX ix86_c_mode_for_suffix
config/pa/pa.c:#undef TARGET_C_MODE_FOR_SUFFIX
config/pa/pa.c:#define TARGET_C_MODE_FOR_SUFFIX pa_c_mode_for_suffix
Others are out of luck with 'q' and 'w' suffixes.
next prev parent reply other threads:[~2012-11-14 22:43 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
2012-11-14 22:31 ` paolo.carlini at oracle dot com
2012-11-14 22:43 ` ubizjak at gmail dot com [this message]
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-D4rU3tLJYh@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).