From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25584 invoked by alias); 4 May 2006 12:08:20 -0000 Received: (qmail 24476 invoked by uid 48); 4 May 2006 12:08:07 -0000 Date: Thu, 04 May 2006 12:08:00 -0000 Message-ID: <20060504120807.24474.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/27417] wrong code or aliasing violation with missed diagnostic? In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pluto at agmk dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-05/txt/msg00353.txt.bz2 List-Id: ------- Comment #2 from pluto at agmk dot net 2006-05-04 12:08 ------- (In reply to comment #1) > This missed diagnostic is known, as enabling a warning here would cause too > much "false" positives. but what about -Wstrict-aliasing=2? it doesn't report anything, so how can i check possible violations with accepted false-positive level? -- pluto at agmk dot net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27417