Skip to content

Move Float16 print tests to their own file and test exhaustively #72859

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

Merged

Conversation

stephentyrone
Copy link
Contributor

We can easily test all 2**16 values, so let's do it. Also now _Float16 is properly supported in clang, so we can pass arguments to CPP that way, which lets us get snan right on more platforms and just generally make things cleaner.

…vely.

We can easily test all 2**16 values, so let's do it. Also now _Float16 is properly supported in clang, so we can pass arguments to CPP that way, which lets us get snan right on more platforms.
@stephentyrone stephentyrone requested review from a team, mikeash and al45tair as code owners April 5, 2024 00:11
@stephentyrone stephentyrone requested a review from tbkka April 5, 2024 00:11
And fixup availability for x86 that was copied from another branch.
@stephentyrone stephentyrone force-pushed the exhaustive-test-float16-printing branch from 3da90d6 to dd72aa3 Compare April 5, 2024 14:31
@stephentyrone
Copy link
Contributor Author

@swift-ci smoke test

Apparently clang/windows (sigh) doesn't define FLT16_MAX in <float.h>,
so we have to keep using the _p interface instead.
@stephentyrone
Copy link
Contributor Author

@swift-ci smoke test

@stephentyrone stephentyrone merged commit 6ac852f into swiftlang:main Apr 5, 2024
@stephentyrone stephentyrone deleted the exhaustive-test-float16-printing branch April 5, 2024 23:55
stephentyrone added a commit that referenced this pull request Apr 19, 2024
) (#73106)

We can easily test all 2**16 values, so let's do it. Also now _Float16 is properly supported in clang, so we can pass arguments to CPP that way, which lets us get snan right on more platforms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants