public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51146] The name clog for a global variable triggers a segfault inside std::pow
Date: Tue, 15 Nov 2011 22:44:00 -0000	[thread overview]
Message-ID: <bug-51146-4-kDi7gyAMN7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51146-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-11-15 22:28:38 UTC ---
I think this is really a duplicate of an issue discussed in various places 
before: libstdc++ relies on C library symbols that are not necessarily 
reserved by the selected version of standard C++, and in particular it 
relies on them in inline code in headers.  This means (a) g++ predefines 
_GNU_SOURCE, causing headers included by the user to make visible symbols 
the user didn't want and (b) the use of symbols in the headers conflicts 
with any symbols of the same name defined by the user.  Fixing this would 
be pretty involved and require close cooperation with libc to provide 
implementation-namespace versions of every such symbol the library needs, 
as I said in bug 36231; a lot of work to get this exactly in accordance 
with the various standards.


  parent reply	other threads:[~2011-11-15 22:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 19:53 [Bug c++/51146] New: " alpha_lc at hotmail dot com
2011-11-15 20:09 ` [Bug libstdc++/51146] " pinskia at gcc dot gnu.org
2011-11-15 20:13 ` alpha_lc at hotmail dot com
2011-11-15 20:21 ` [Bug c++/51146] " paolo.carlini at oracle dot com
2011-11-15 20:33 ` pinskia at gcc dot gnu.org
2011-11-15 20:33 ` paolo.carlini at oracle dot com
2011-11-15 22:44 ` joseph at codesourcery dot com [this message]
2011-11-15 23:11 ` paolo.carlini at oracle dot com
2011-11-15 23:29 ` redi at gcc dot gnu.org
2011-11-16  0:13 ` paolo.carlini at oracle dot com
2021-09-30  9:14 ` pinskia at gcc dot gnu.org
2021-09-30 10:02 ` redi at gcc dot gnu.org
2021-09-30 10:04 ` redi 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-51146-4-kDi7gyAMN7@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).