From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28564 invoked by alias); 5 May 2006 15:10:44 -0000 Received: (qmail 28488 invoked by uid 48); 5 May 2006 15:10:35 -0000 Date: Fri, 05 May 2006 15:10:00 -0000 Message-ID: <20060505151035.28487.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/msg00517.txt.bz2 List-Id: ------- Comment #4 from pluto at agmk dot net 2006-05-05 15:10 ------- (In reply to comment #3) > You cannot. Though you can try extending c-common.c:strict_aliasing_warning > and > cp/typeck.c:build_reinterpret_cast_1 to warn in this case. sorry, but i don't know compiler internals to do this. btw, maybe we should collect in one PR examples of undetected aliasing violations for future work on better detection? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27417