This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Make alias_sets_conflict_p less conservative

From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
To: rguenther at suse dot de
Cc: dberlin at dberlin dot org, gcc-patches at gcc dot gnu dot org
Date: Wed, 05 Mar 2008 06:32:35 EST
Subject: Re: [PATCH] Make alias_sets_conflict_p less conservative
References: <Pine.LNX.4.64.0803042155430.4133@zhemvz.fhfr.qr> <10803042355.AA00168@vlsi1.ultra.nyu.edu> <4aca3dc20803041620g70075ae3h40d22a4531ad7566@mail.gmail.com> <10803050136.AA01130@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0803051057420.4133@zhemvz.fhfr.qr>

> Yes, char is assigned alias set zero.  And this is correct.
> 
>   char a[4];
>   int *p;
> 
> an access through *p conflicts with a. 

By what rule?  I was under the impression that this was a special rule
applying to "char *".

Follow-Ups:
- Re: [PATCH] Make alias_sets_conflict_p less conservative
  - From: Richard Guenther

References:
- [PATCH] Make alias_sets_conflict_p less conservative
  - From: Richard Guenther
- Re: [PATCH] Make alias_sets_conflict_p less conservative
  - From: Richard Kenner
- Re: [PATCH] Make alias_sets_conflict_p less conservative
  - From: Daniel Berlin
- Re: [PATCH] Make alias_sets_conflict_p less conservative
  - From: Richard Kenner
- Re: [PATCH] Make alias_sets_conflict_p less conservative
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]