Displaying 3 results from an estimated 3 matches for "2dpoint".
Did you mean:
endpoint
2019 Aug 21
2
Floating point operations with specific rounding and exception properties
...gt; behavior different from the default, it should be represented by
>> constrained intrinsic (
>> http://llvm.org/docs/LangRef.html#constrained-floating-point-intrinsics
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__llvm.org_docs_LangRef.html-23constrained-2Dfloating-2Dpoint-2Dintrinsics&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=O_4M49EtSpZ_-BQYeigzGv0P4__noMcSu2RYEjS1vKs&m=fTfAlQ0FHnQez3xiw8VnBL1XaxmBqn_-WD5E0mh4GrY&s=5LUnqvzxtBJcUMLBjiVfnEwD53rKH1ZIQmEcvXhbEdo&e=>).
>> An important point is that according to the current design decision, if...
2019 Aug 20
3
Floating point operations with specific rounding and exception properties
Hi all,
During the review of https://reviews.llvm.org/D65997 an issue was revealed,
which relates to the decision of how compiler should represents constrained
floating point operations.
If a floating point operation requires rounding mode or exception behavior
different from the default, it should be represented by constrained
intrinsic (
2020 Sep 04
2
using experimental intrinsics failed
Hi Craig:
I tried that, now the function is like this:
; Function Attrs: norecurse nounwind readnone ssp uwtable
define { double, double } @add(double, double, double, double) local_unnamed_addr #0 {
%5 = call double @llvm.experimental.constrained.fadd(double %0, double %2, metadata !"round.downward", metadata !"fpexcept.ignore")
%6 = fadd double %1, %3