[llvm-bugs] [Bug 52577] New: Signaling NaNs are seem supported but __SUPPORT_SNAN__ is not defined

via llvm-bugs llvm-bugs at lists.llvm.org
Mon Nov 22 03:31:20 PST 2021


            Bug ID: 52577
           Summary: Signaling NaNs are seem supported but __SUPPORT_SNAN__
                    is not defined
           Product: clang
           Version: 13.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C
          Assignee: unassignedclangbugs at nondot.org
          Reporter: pavel.morozkin 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

Note: this may not be a bug, but the subject needs a clarification.

This code:
#define _WANT_SNAN
#ifdef __SUPPORT_SNAN__
#pragma message "__SUPPORT_SNAN__ is defined"
#pragma message "__SUPPORT_SNAN__ is not defined"

compiled with:
$ clang -std=c11 -pedantic -Wall -Wextra -ffp-model=strict -c

leads to:
<source>:5:9: warning: __SUPPORT_SNAN__ is not defined [-W#pragma-messages]

However, according to some tests signaling NaNs are supported.

Then what is the real reason to not define __SUPPORT_SNAN__?

It may be useful to mention the status of support of signaling NaNs in User's
Manual: https://clang.llvm.org/docs/UsersManual.html.

Version: clang 13.0.0 on x86_64 on Linux

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/20211122/8269429a/attachment.html>

More information about the llvm-bugs mailing list