From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4698 invoked by alias); 25 Nov 2004 17:48:23 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 4459 invoked from network); 25 Nov 2004 17:48:19 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sourceware.org with SMTP; 25 Nov 2004 17:48:19 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA07194; Thu, 25 Nov 04 12:52:50 EST Date: Thu, 25 Nov 2004 18:03:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10411251752.AA07194@vlsi1.ultra.nyu.edu> To: nathan@codesourcery.com Subject: Re: [RFC] ignoring type alias conflicts between structures and scalars Cc: gcc@gcc.gnu.org X-SW-Source: 2004-11/txt/msg00981.txt.bz2 your example is different, in that the int lvalue is not some arbitrary pointer dereference, but a known variable. Yes, I think that's the key. The alias_sets_conflict_p routine was meant originally for an RTL environment where every MEM was potentially a pointer dereference (yes, we knew some of those that weren't, but didn't do much with that knowlege). If you want to distinguish between pointers to a type and variables of that type, you don't have to do the symmetric test.