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] Fix questionable code in objects_must_conflict_p

From: Olivier Hainque <hainque at adacore dot com>
To: Eric Botcazou <ebotcazou at adacore dot com>
Cc: Ian Lance Taylor <ian at airs dot com>, gcc-patches at gcc dot gnu dot org,hainque at adacore dot com
Date: Wed, 9 Nov 2005 09:16:05 +0100
Subject: Re: [PATCH] Fix questionable code in objects_must_conflict_p
References: <200511081554.13280.ebotcazou@adacore.com> <m3u0enq8q3.fsf@gossamer.airs.com> <200511082344.35800.ebotcazou@adacore.com>

Eric Botcazou wrote:
> > Isn't this the same as changing the initial conditional to be
> >     if (t1 == 0 || t2 == 0)
> >       return 0;
> > ?
> 
> Sure.

 I'm not so sure :)

 Consider (t1 == 0 && t2 != 0 && alias_set (t2) == 0).

Follow-Ups:
- Re: [PATCH] Fix questionable code in objects_must_conflict_p
  - From: Eric Botcazou
- Re: [PATCH] Fix questionable code in objects_must_conflict_p
  - From: Ian Lance Taylor

References:
- [PATCH] Fix questionable code in objects_must_conflict_p
  - From: Eric Botcazou
- Re: [PATCH] Fix questionable code in objects_must_conflict_p
  - From: Ian Lance Taylor
- Re: [PATCH] Fix questionable code in objects_must_conflict_p
  - From: Eric Botcazou

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