Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Feb 2003 04:02:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Feb 2003 04:02:48 -0500 Received: from ns.suse.de ([213.95.15.193]:34830 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Tue, 11 Feb 2003 04:02:47 -0500 To: Horst von Brand Cc: Art Haas , Linux Kernel Mailing List Subject: Re: Is -fno-strict-aliasing still needed? X-Yow: I've got a COUSIN who works in the GARMENT DISTRICT... From: Andreas Schwab Date: Tue, 11 Feb 2003 10:12:31 +0100 In-Reply-To: <200302110714.h1B7EA3A006209@eeyore.valparaiso.cl> (Horst von Brand's message of "Tue, 11 Feb 2003 08:14:09 +0100") Message-ID: User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.3.50 (ia64-suse-linux) References: <200302110714.h1B7EA3A006209@eeyore.valparaiso.cl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 990 Lines: 28 Horst von Brand writes: |> Art Haas said: |> > I ask because I've just built a kernel without using that flag - |> > linus-2.5 BK from this morning, probably missing the 2.5.60 release by |> > a few hours. |> |> The problem with strict aliasing is that it allows the compiler to assume |> that in: |> |> void somefunc(int *foo, int *bar) |> |> foo and bar will _*never*_ point to the same memory area This is wrong. Only if they are declared restrict. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 N?rnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/