public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/36231] ostream includes unistd.h outside namespace std, polluting
Date: Thu, 21 Apr 2011 00:03:00 -0000	[thread overview]
Message-ID: <bug-36231-4-LlwB5S3KSZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-36231-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-04-21 00:02:02 UTC ---
Thanks Ralf, I didn't know AC_CHECK_SIZEOF and AC_CHECK_ALIGNOF even existed,
in similar situations probably I would have dumbly re-invented both basing on
AC_COMPUTE_INT ;)

Otherwise, about the issue which prompted my question, seems still tough,
because actually gthr.h is included by a few different headers, also in locale,
not just via the path explained in the PR. Frankly, I don't know how much we
can get into this within the existing ABI... To Ivan I have to remember that we
don't control in general the underlying .h headers, it's the usual question,
how far we can go without assuming much about the C headers and of course
without changing the headers themselves...


  parent reply	other threads:[~2011-04-21  0:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-36231-4@http.gcc.gnu.org/bugzilla/>
2011-04-20 15:18 ` redi at gcc dot gnu.org
2011-04-20 18:42 ` paolo.carlini at oracle dot com
2011-04-20 18:44 ` paolo.carlini at oracle dot com
2011-04-20 20:37 ` paolo.carlini at oracle dot com
2011-04-20 21:07 ` igodard at pacbell dot net
2011-04-20 23:10 ` rwild at gcc dot gnu.org
2011-04-21  0:03 ` paolo.carlini at oracle dot com [this message]
2011-04-21  0:23 ` igodard at pacbell dot net
2011-07-15 12:10 ` paolo.carlini at oracle dot com
2008-05-13 19:46 [Bug libstdc++/36231] New: " igodard at pacbell dot net
2008-05-13 20:04 ` [Bug libstdc++/36231] " pinskia at gcc dot gnu dot org
2010-04-29 23:16 ` redi at gcc dot gnu dot org
2010-04-29 23:36 ` igodard at pacbell dot net
2010-04-30  1:02 ` redi at gcc dot gnu dot org
2010-04-30  1:04 ` paolo dot carlini at oracle dot com
2010-04-30  5:28 ` igodard at pacbell dot net
2010-04-30  9:32 ` paolo dot carlini at oracle dot com
2010-04-30  9:51 ` redi at gcc dot gnu dot org
2010-04-30 14:24 ` igodard at pacbell dot net
2010-04-30 14:42 ` joseph at codesourcery dot com
2010-04-30 15:58 ` redi at gcc dot gnu dot 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-36231-4-LlwB5S3KSZ@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).