From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30572 invoked by alias); 27 Jan 2008 11:45:20 -0000 Received: (qmail 30149 invoked by uid 48); 27 Jan 2008 11:44:35 -0000 Date: Sun, 27 Jan 2008 12:36:00 -0000 Message-ID: <20080127114435.30148.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/26099] support for type traits is not available In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pcarlini at suse dot de" 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: 2008-01/txt/msg03313.txt.bz2 ------- Comment #12 from pcarlini at suse dot de 2008-01-27 11:44 ------- Yes, I noticed. Frankly, I'm not really worried because of the nature of the tests: the checks can give different answers depending on whether the compiler is able or not to figure out that a given function cannot throw. For some reason (which I agree would be interesting to understand in better detail), -fpic/PIC makes makes more difficult for the compiler to assess that a function cannot really throw. I'm not sure about the best way to fix that: we could just zap those specific tests which have such "instability", or condition the result on -fpic/PIC via macros, or something better. I would probably be tempted to go the first route, for 4.3.0., at least. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26099