public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59087] Issues including complex.h in C++11/1y mode because of C's complex.h
Date: Thu, 14 Nov 2013 15:43:00 -0000 [thread overview]
Message-ID: <bug-59087-4-VKJQxCyGbe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59087-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59087
--- Comment #8 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Ed Smith-Rowland from comment #7)
> g++ is working as intended.
Thanks a lot for the investigation. Do you think the error message: "unable to
find numeric literal operator" could additionally point out that
-fext-numeric-literals or -std=gnu++11 would allow the code to work, for
suffixes for which that is the case? That would have saved you a lot of
investigation time ;-)
next prev parent reply other threads:[~2013-11-14 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 12:49 [Bug libstdc++/59087] New: including complex.h in C++11/1y mode should not include " kikairoya at gmail dot com
2013-11-12 13:16 ` [Bug libstdc++/59087] " glisse at gcc dot gnu.org
2013-11-12 14:23 ` kikairoya at gmail dot com
2013-11-12 14:41 ` [Bug libstdc++/59087] Issues including complex.h in C++11/1y mode because of " glisse at gcc dot gnu.org
2013-11-13 15:47 ` glisse at gcc dot gnu.org
2013-11-14 0:29 ` 3dw4rd at verizon dot net
2013-11-14 11:58 ` 3dw4rd at verizon dot net
2013-11-14 15:30 ` 3dw4rd at verizon dot net
2013-11-14 15:43 ` glisse at gcc dot gnu.org [this message]
2014-01-02 22:46 ` glisse at gcc dot gnu.org
2014-01-02 23:04 ` glisse at gcc dot gnu.org
2014-09-03 19:00 ` vlovich at gmail dot com
2014-09-03 19:05 ` vlovich at gmail dot com
2014-09-03 19:20 ` glisse at gcc dot gnu.org
2014-09-03 19:37 ` vlovich at gmail dot com
2014-09-03 19:44 ` glisse at gcc dot gnu.org
2014-09-04 4:52 ` vlovich at gmail dot com
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-59087-4-VKJQxCyGbe@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).