Displaying 2 results from an estimated 2 matches for "inaccessible_mem_only".
2019 Oct 03
2
[RFC] Using basic block attributes to implement non-default floating point environment
...bine/replace/... regular floating operations in the presence
of constraint intrinsics because they do not impact each other (other
than def-use). If that understanding is correct, and this is a problem,
then I doubt that we want basic block attributes. Also, given that the
constraint intrinsics are inaccessible_mem_only, optimizations will work
with them as they work with other opaque instructions for which certain
effects are known.
(Btw. is it intentional that these can unwind?)
> This philosophy is key to the way that we’re approaching FPENV
> support. One of the primary goals is that any optimization t...
2019 Oct 01
7
[RFC] Using basic block attributes to implement non-default floating point environment
Hi all,
This proposal is aimed at support of floating point environment, in which
some properties like rounding mode or exception behavior differ from those
used by default. This include in particular support of 'pragma STDC
FENV_ACCESS', 'pragma STDC FENV_ROUND' as well as some other related
facilities.
Problem
On many processors use of non-default floating mode requires