Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SR-2403] Recognize __builtin_{huge_val,inf,nan}() macros #45010

Open
belkadan opened this issue Aug 18, 2016 · 0 comments
Open

[SR-2403] Recognize __builtin_{huge_val,inf,nan}() macros #45010

belkadan opened this issue Aug 18, 2016 · 0 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. c/c++ macros c interop Feature: Interoperability with C compiler The Swift compiler in itself good first issue Good for newcomers

Comments

@belkadan
Copy link
Contributor

Previous ID SR-2403
Radar rdar://problem/19051485
Original Reporter @belkadan
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, ClangImporter, Macros, StarterBug
Assignee None
Priority Medium

md5: c8e64f9c66f50b498cedbe9171dcc5a6

Issue Description:

__builtin_huge_val(), __builtin_nan(""), and __builtin_inf() are often used to define macros that evaluate to IEEE infinity or NaN. We could recognize these patterns and import them as aliases for Double.infinity/nan (or mark them unavailable in favor of the native Swift type properties).
@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@AnthonyLatsis AnthonyLatsis added the c interop Feature: Interoperability with C label Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. c/c++ macros c interop Feature: Interoperability with C compiler The Swift compiler in itself good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@belkadan @AnthonyLatsis