This is the mail archive of the
mailing list for the GCC project.
Re: operator new returns nonzero
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Marc Glisse <marc dot glisse at inria dot fr>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Sat, 7 Sep 2013 14:24:22 -0500
- Subject: Re: operator new returns nonzero
- Authentication-results: sourceware.org; auth=none
- References: <alpine dot DEB dot 2 dot 02 dot 1309071206340 dot 19326 at stedding dot saclay dot inria dot fr> <alpine dot DEB dot 2 dot 10 dot 1309071804080 dot 3585 at laptop-mg dot saclay dot inria dot fr> <CAAiZkiCj8_p-Hnu-2Ymc_p6Vmv_-6Xi8O8HOs26whnkVcK=0SA at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1309071934100 dot 3585 at laptop-mg dot saclay dot inria dot fr>
On Sat, Sep 7, 2013 at 12:59 PM, Marc Glisse <email@example.com> wrote:
>> Furthermore, I do think that the compiler should have special nodes
>> for both standard placement new and the global operator new functions,
> That's one way to do it. Since this is the first time I look at those, I
> don't really see the advantage compared to the current status, but I trust
> you. What would you do with this special-node placement new?
placement new really is about "calling" a contractor, and marking the
beginning of the lifetime of a new object, hence aiding lifetime-based
> Keep it as is
> until after vrp so we can use the !=0 property and then expand it to its
> first argument? Or expand it early to the equivalent of the library code I
> wrote above?
>> as I explained in previous messages.
> I couldn't find them, sorry if they contained information that makes this
> post irrelevant.