On Sep 9, 2013, at 5:41 AM, Gabriel Dos Reis <g...@integrable-solutions.net> wrote: > On Mon, Sep 9, 2013 at 4:06 AM, Richard Biener > <richard.guent...@gmail.com> wrote: >> On Sat, Sep 7, 2013 at 11:00 PM, Marc Glisse <marc.gli...@inria.fr> wrote: >>> On Sat, 7 Sep 2013, Mike Stump wrote: >>> >>>> On Sep 7, 2013, at 12:27 PM, Marc Glisse <marc.gli...@inria.fr> wrote: >>>>> >>>>> Now flag_check_new should probably disable this optimization… >>>> >>>> >>>> Yes, this why my point. >>> >>> >>> Ok, here it is (again, no proper testing until bootstrap is fixed) >> >> I wonder what happens on targets where 0 is a valid address of an object >> (stated by !flag_delete_null_pointer_checks)? > > We should distinguish between front-end notion of null pointer, > and backend notion of address zero. The language, and therefore > the front-end, does not allow an object to have 'this' value to be > a null pointer, nor does is allow 'operator new' to return null pointer.
You've failed to understand g++. Please seek to understand the compiler, before you weigh in.
