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, 02 Jan 2014 22:46:00 -0000	[thread overview]
Message-ID: <bug-59087-4-lQw7KI2Dyw@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 #9 from Marc Glisse <glisse at gcc dot gnu.org> ---
Author: glisse
Date: Thu Jan  2 22:45:56 2014
New Revision: 206304

URL: http://gcc.gnu.org/viewcvs?rev=206304&root=gcc&view=rev
Log:
2014-01-02  Marc Glisse  <marc.glisse@inria.fr>

    PR c++/59087
gcc/cp/
    * parser.c (cp_parser_userdef_numeric_literal): Mention
    -fext-numeric-literals in the message.


Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/parser.c


  parent reply	other threads:[~2014-01-02 22:46 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
2014-01-02 22:46 ` glisse at gcc dot gnu.org [this message]
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-lQw7KI2Dyw@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).