From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-374085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 19013 invoked by alias); 15 Nov 2011 23:06:20 -0000
Received: (qmail 19002 invoked by uid 22791); 15 Nov 2011 23:06:19 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Nov 2011 23:05:23 +0000
From: "paolo.carlini at oracle 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 23:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51146-4-8DvwLiyLcT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51146-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51146-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-11/txt/msg01581.txt.bz2

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?