[llvm-bugs] [Bug 44571] New: clang fails to set strictfp function attribute

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Jan 16 10:32:15 PST 2020


            Bug ID: 44571
           Summary: clang fails to set strictfp function attribute
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: mib.bugzilla at gmail.com
                CC: blitzrakete at gmail.com, dgregor at apple.com,
                    erik.pilkington at gmail.com, llvm-bugs at lists.llvm.org,
                    richard-llvm at metafoo.co.uk

I got an email about this issue:  It looks like clang isn't setting the
strictfp attribute added to the functions that use constrained intrinsics in
all cases. This problem has been identified in unary conversions, builtins, and

This fails to set the attribute, but uses constrained functions

float _Complex foo(float _Complex a, float _Complex b) {
return a + b;

Or this compiled with -fno-math-errno

float foo(float a, float b) {
return sinf(a);

Here's another example, https://godbolt.org/z/bcVV6A 

Andy Kaylor suggested "Can’t we mark functions with the strictfp attribute any
time a constrained mode is enabled within the function, regardless of whether
or not it uses an FP operation?  For example, functions get the
"unsafe-fp-math"="false" attribute without regard to whether or not they
contain fp operations. I would expect strictfp to be the same."

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200116/29c940cd/attachment.html>

More information about the llvm-bugs mailing list