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++/54249] [C++11] No ::nullptr_t in header <stddef.h>
Date: Tue, 14 Aug 2012 10:49:00 -0000	[thread overview]
Message-ID: <bug-54249-4-SCUMAUvEUq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54249-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54249

--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> 2012-08-14 10:48:48 UTC ---
(In reply to comment #5)
> It's true however, that, as I mentioned already somewhere, in general our
> implementation doesn't have control over the underlying *.h headers.

Although it does have control over potential *.h headers it ships and puts
first in the include path (as it does for complex.h and fenv.h for instance).

> Thus, it seems mildly inconsistent to add things only to the *few* *.h
> headers over which we do have control.

Grab the low-hanging fruits?

(sorry Daniel, conversations seems to have a way to start when we don't want
them to...)


  parent reply	other threads:[~2012-08-14 10:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14  8:04 [Bug libstdc++/54249] New: " daniel.kruegler at googlemail dot com
2012-08-14  8:05 ` [Bug libstdc++/54249] " daniel.kruegler at googlemail dot com
2012-08-14  9:36 ` glisse at gcc dot gnu.org
2012-08-14  9:52 ` daniel.kruegler at googlemail dot com
2012-08-14 10:36 ` glisse at gcc dot gnu.org
2012-08-14 10:38 ` paolo.carlini at oracle dot com
2012-08-14 10:49 ` glisse at gcc dot gnu.org [this message]
2012-08-14 10:50 ` redi at gcc dot gnu.org
2012-08-14 10:52 ` paolo.carlini at oracle dot com
2012-08-14 10:56 ` paolo.carlini at oracle dot com
2012-08-14 10:59 ` redi at gcc dot gnu.org
2012-08-14 11:02 ` daniel.kruegler at googlemail dot com
2012-08-14 11:10 ` daniel.kruegler at googlemail dot com
2012-09-28 10:01 ` [Bug c++/54249] " paolo.carlini at oracle dot com
2012-09-28 10:03 ` paolo.carlini at oracle dot com
2012-10-06 22:44 ` paolo at gcc dot gnu.org
2012-10-06 22:47 ` paolo.carlini at oracle 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-54249-4-SCUMAUvEUq@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).