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: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
To: iant at google dot com
Cc: dberlin at dberlin dot org, ebotcazou at adacore dot com, gcc-patches at gcc dot gnu dot org
Date: Sun, 10 Jun 2007 14:22:32 EDT
Subject: Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
References: <m3y7itm484.fsf@localhost.localdomain> <200706091938.46247.ebotcazou@adacore.com> <4aca3dc20706091940w7bf465f0kb6f86b5d22480e4f@mail.gmail.com> <200706100746.26764.ebotcazou@adacore.com> <m3ps43n0gm.fsf@localhost.localdomain>

> I agree that in principle this could be done using type variants.  But
> in practice I think it is more reliable to make it a property of the
> pointer rather than of the type of the pointer.

What do you mean?  Suppose I have a function returning such a pointer.
Where is the "property"?  Don't these things *have* to be on the type?

Follow-Ups:
- Re: PATCH RFA: PR 29286: Handle placement new aliasing issues
  - From: Ian Lance Taylor

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: Daniel Berlin
- 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

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