From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28987 invoked by alias); 6 Feb 2010 17:52:38 -0000 Received: (qmail 28955 invoked by uid 48); 6 Feb 2010 17:52:28 -0000 Date: Sat, 06 Feb 2010 17:52:00 -0000 Message-ID: <20100206175228.28954.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/27340] valarray uses __cos which may conflict with libm functions In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "marc dot glisse at normalesup dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-02/txt/msg00485.txt.bz2 ------- Comment #9 from marc dot glisse at normalesup dot org 2010-02-06 17:52 ------- (In reply to comment #8) > It seems this can be safely closed as invalid, there is no reason why > std::__cos should be wrong. Marking this as invalid means that we can never include solaris libc headers with __cplusplus >= 199711 (which declare std::__cos as a function) without fixincluding them beyond recognition. Even without this problem on solaris, using in libstdc++ names as generic as std::__cos for a functionality limited to valarray doesn't seem like an ideal naming convention. But then, the choice is yours, I am not ticking the "reopen" box. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27340