From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9510 invoked by alias); 1 Oct 2008 14:20:30 -0000 Received: (qmail 8297 invoked by uid 48); 1 Oct 2008 14:19:07 -0000 Date: Wed, 01 Oct 2008 14:20:00 -0000 Message-ID: <20081001141907.8296.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug middle-end/22207] Spurious 'might be used uninitialized' warnings in STL headers with -O2 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave dot korn at artimi dot com" 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-10/txt/msg00031.txt.bz2 ------- Comment #5 from dave dot korn at artimi dot com 2008-10-01 14:19 ------- Sorry mate, all 3.x compilers are way past end-of-life now; there will never be another release. Your best bet is to hand-edit the header files in your local install. I don't remember the exact recipe, but of the two places where this bug crops up, one can be worked around by adding "__attribute__ ((__unused__))" to the relevant variable declaration, and the other one has to be fixed by adding "__attribute__ ((__noinline__))" to the function declaration. I haven't tested these workaround for performance impact. Shouldn't be too bad if you're not calling the functions from the middle of a loop that runs millions of times. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22207