[PATCH] Skip ubsan internal fns in tail-merge

Tom de Vries Tom_deVries@mentor.com
Mon Mar 7 09:49:00 GMT 2016


[ was: Re: [PATCH 3/3] Fix ubsan tests by disabling of an optimization. ]

On 10/07/15 22:11, Jeff Law wrote:
> On 07/10/2015 02:19 AM, Richard Biener wrote:
>>
>> But the warning on the "bogus" line will still be warranted, so user
>> goes and
>> fixes it.
> But when the user gets the "bogus" line, he may look at the code and
> determine that the reported line can't possibly be executed -- so they
> get confused, assume the warning is bogus and ignore it.
>
>
>
>   Then tail-merge no longer applies and he gets the warning on the
>> other warranted line.
> That assumes that we'd get to both paths.  We may not.  The paths may be
> totally independent.
>

IIUC, the conclusion of this discussion (starting at 
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg00758.html ) is that we 
want to disable tail-merge for ubsan internal functions?

This patch implements that.

Should the asan internal function (ASAN_CHECK) be handled in the same 
way, as suggested here ( 
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg00776.html )?

OK for stage4 trunk if bootstrap and reg-test succeeds?

Thanks,
- Tom

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Skip-ubsan-internal-fns-in-tail-merge.patch
Type: text/x-patch
Size: 1742 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20160307/0df4055f/attachment.bin>


More information about the Gcc-patches mailing list