On Sat, Apr 09, 2016 at 01:21:06PM +0200, Richard Biener wrote:
> To followup myself here - we can also make sure the function doesn't become
> pure/const.
>
> Similar issues exist with pure/const functions with ops with undefined
> overflow (and code gen taking advantage of that).
> So it's not only trapping that needs to be guarded against... :/
But then we'd probably want 2 categories, keep pure/const meaning it had
(that allows trapping/FPU exceptions, because, aren't most of libm const
functions in this category?), and then have another attributes for functions
that can't trap/don't use FPU etc.
Anyway, I've committed the patch and will change the PR to be 7/Regression,
so that it is not forgotten.
Jakub
