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: dberlin at dberlin dot org
Cc: gcc-patches at gcc dot gnu dot org, rguenther at suse dot de
Date: Tue, 04 Mar 2008 20:36:53 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>

> This is because the the type based rules (at least for C) say "access
> through pointer char can validly alias anything" but not "access
> through pointer to anything can validly alias char".

I note there is no char * in sight there.  Are we, by some chance, assigning
char to alias set zero? That seems wrong.  Rather char * should be
marked as type-pointed-to-can-alias-all.

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

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