This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] fix PR39701 testsuite failures
- From: Ian Lance Taylor <iant at google dot com>
- To: Richard Guenther <richard dot guenther at gmail dot com>
- Cc: Paolo Bonzini <bonzini at gnu dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>, GNU GFortran <fortran at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 10 Apr 2009 07:39:47 -0700
- Subject: Re: [PATCH] fix PR39701 testsuite failures
- References: <49DEF29F.4020501@gnu.org> <84fc9c000904100114x4a185a4bhd99c249724b0361@mail.gmail.com>
Richard Guenther <richard.guenther@gmail.com> writes:
> On Fri, Apr 10, 2009 at 9:17 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
>
>> ÂObservation: I think however that it does not make sense to have
>> Â-fdelete-null-pointer-checks only at -O2 or higher -- it it is not
>> Âan optimization option, rather it describes the semantics of the
>> Âtarget, and it should be enabled uniformly at all optimization levels.
>> ÂIf there are places that we consider optimizations, they should be
>> Âguarded by "(optimize >= 2 && flag_delete_null_pointer_checks).
>
> I agree. A patch to make -fdelete-null-pointer-checks enabled by
> default is pre-approved (it likely needs documentation changes).
At -O0, if I write
if (&i == 0) abort();
then I need to be able to set a breakpoint on that line. I'm OK with
the patch if that property is preserved.
Ian