From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16736 invoked by alias); 9 Nov 2004 19:27:30 -0000 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 Received: (qmail 16562 invoked from network); 9 Nov 2004 19:27:23 -0000 Received: from unknown (HELO mprelay.uc.edu) (129.137.3.48) by sourceware.org with SMTP; 9 Nov 2004 19:27:23 -0000 Received: from [10.44.106.140] (zhivago.geop.uc.edu [10.44.106.140]) by mprelay.uc.edu (MOS 3.4.7-GR) with ESMTP id BYJ68804; Tue, 9 Nov 2004 14:27:22 -0500 (EST) In-Reply-To: <200411092023.46209.torger@ludd.luth.se> References: <200411092023.46209.torger@ludd.luth.se> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6026605A-3285-11D9-9E21-000A95D692F4@physics.uc.edu> Content-Transfer-Encoding: 7bit Cc: gcc-bugs@gcc.gnu.org, Andreas Schwab From: Andrew Pinski Subject: Re: No warning when breaking strict-aliasing rules despite -Wstrict-aliasing Date: Tue, 09 Nov 2004 19:27:00 -0000 To: Anders Torger X-SW-Source: 2004-11/txt/msg01160.txt.bz2 List-Id: On Nov 9, 2004, at 2:23 PM, Anders Torger wrote: > gcc 2.95 generates correct code. It just generates code which you expected not the code which the C standard says it is undefined (oh by the way we could wipe your HD if you invoke undefined behavior). Also a DR report says we cannot error out on undefined code because it might not execute at all. Thanks, Andrew Pinski