This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/51146] The name clog for a global variable triggers a segfault inside std::pow
- From: "paolo.carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 15 Nov 2011 23:05:17 +0000
- Subject: [Bug c++/51146] The name clog for a global variable triggers a segfault inside std::pow
- Auto-submitted: auto-generated
- References: <bug-51146-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51146
--- Comment #7 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-11-15 23:05:17 UTC ---
I just want to reiterate that the c++ library headers never name clog, only
__builtin_clog (and of course only when the underlying libc provides the
corresponding clog, in case runtime library calls are actually required). I
don't see why this way of using a __builtin* facility should give problems.
Would it be difficult to change the compiler to decouple completely, eg,
__builtin_clog from clog, in such a way that if the user or anything else
fiddles with the latter, the former is not affected, as if it were a completely
different, unrelated, name?