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 RFA: PR 29286: Handle placement new aliasing issues

From: Ian Lance Taylor <iant at google dot com>
To: Eric Botcazou <ebotcazou at adacore dot com>
Cc: gcc-patches at gcc dot gnu dot org, "Daniel Berlin" <dberlin at dberlin dot org>
Date: 11 Jun 2007 12:11:19 -0700
Subject: Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
References: <m3y7itm484.fsf@localhost.localdomain> <200706112025.15792.ebotcazou@adacore.com> <m37iqajq2x.fsf@localhost.localdomain> <200706112111.05677.ebotcazou@adacore.com>

Eric Botcazou <ebotcazou@adacore.com> writes:

> > As far as I can see that SMT would have to alias every other SMT in
> > order to correctly implement CHANGE_DYNAMIC_TYPE_EXPR, so I don't
> > think this would actually pessimize less.
> 
> I don't think so.  If you say that CHANGE_DYNAMIC_TYPE_EXPR is a special 
> escape site and trace back which variables escape at it (like for variables 
> that escape in the call-clobbered sense), you could only include those 
> variables in the SMT.

Seems plausible, but I'm not sure it's significantly simpler than what
I implemented.

Ian

Follow-Ups:
- Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
  - From: Daniel Berlin

References:
- PATCH RFA: PR 29286: Handle placement new aliasing issues
  - From: Ian Lance Taylor
- Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
  - From: Eric Botcazou
- Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
  - From: Ian Lance Taylor
- Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
  - From: Eric Botcazou

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