This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++] Add -fnull-this-pointer
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Markus Trippelsdorf <markus at trippelsdorf dot de>
- Cc: Jakub Jelinek <jakub at redhat dot com>, Jan Hubicka <hubicka at ucw dot cz>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Jason Merrill <jason at redhat dot com>, mliska at suse dot cz, tbsaunde+gcc at tbsaunde dot org
- Date: Mon, 7 Mar 2016 13:27:00 +0100
- Subject: Re: [C++] Add -fnull-this-pointer
- Authentication-results: sourceware.org; auth=none
- References: <20160119121143 dot GF5273 at kam dot mff dot cuni dot cz> <20160307113500 dot GA304 at x4> <CAFiYyc3HCjPu-v1ng9kciz3W2bv18b5h5PY5kdMmg07f0i4hUQ at mail dot gmail dot com> <20160307120301 dot GU3017 at tucnak dot redhat dot com> <20160307121443 dot GB304 at x4>
On Mon, Mar 7, 2016 at 1:14 PM, Markus Trippelsdorf
<markus@trippelsdorf.de> wrote:
> On 2016.03.07 at 13:03 +0100, Jakub Jelinek wrote:
>> On Mon, Mar 07, 2016 at 12:57:20PM +0100, Richard Biener wrote:
>> > (no strong opinion about that - but for example the recent -flifetime-dse
>> > strengthening fallout is similar)
>>
>> -flifetime-dse change is different, we default to -flifetime-dse=2, but have
>> a way for broken packages to workaround their bugs, so that situation is the
>> same as with -fno-delete-null-pointer-checks.
>
> If the situation was the same there would be no -flifetime-dse=2 flag at
> all. Affected users would be told to use -fno-lifetime-dse for broken
> code, just like they are told to use -fno-delete-null-pointer-checks.
Yes, I said I would have told them that. But appearantly Jason had a
different opinion...
Richard.
> --
> Markus