From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26849 invoked by alias); 27 Dec 2010 19:17:32 -0000 Received: (qmail 26828 invoked by uid 22791); 27 Dec 2010 19:17:30 -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; Mon, 27 Dec 2010 19:17:26 +0000 From: "pogma at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40411] -std=c99 does not enable c99 mode in Solaris C library X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pogma at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ro at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Mon, 27 Dec 2010 19:17:00 -0000 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-12/txt/msg02698.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40411 pogma@gcc.gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pogma at gcc dot gnu.org --- Comment #20 from pogma at gcc dot gnu.org 2010-12-27 19:17:18 UTC --- (In reply to comment #19) > Whether using it is enabled via -std or > not, linking to values-xpg6.o can cause unexpected behaviour for applications > or shared objects. Yes, it can, and that behaviour change is surprising, especially if relinking a library with a newer gcc (using the same flags as it was linked with using an older version of the compiler) can cause clients of that library to stop working or to behave in a different manner. If a user really wants the xpg6 behaviour from libc they can simply add the relevant object file to their output or even just define the __xpg4 and __xpg6 symbols in their application, or, as Bruno suggests - use gnulib.