From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15442 invoked by alias); 27 Jan 2008 13:35:34 -0000 Received: (qmail 15222 invoked by uid 48); 27 Jan 2008 13:34:48 -0000 Date: Sun, 27 Jan 2008 14:14:00 -0000 Message-ID: <20080127133448.15221.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/msg03324.txt.bz2 ------- Comment #14 from pcarlini at suse dot de 2008-01-27 13:34 ------- (In reply to comment #13) > If a function isn't marked nothrow and the function can be overridden by a > shared library (that is, it doesn't bind locally), the compiler cannot derive > such property from its body. Thanks for the details. > (I didn't look at the tests, but usually marking the affected functions > nothrow or making them bind locally works around this problem). Well, the functions in those specific tests aren't marked no throw on purpose (we do have other tests for the no throw variants), because I was exactly testing that in some specific cases the C++ front-end is able to figure out by itself that the function doesn't really throw. All in all I'm now thinking that it's good to have such tests, we should only conditionalize the result of the tests on -fpic/PIC, I suppose we do have a macro for that?!? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26099