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

Disable f16 on platforms that have recursion problems #730

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

tgross35
Copy link
Contributor

@tgross35 tgross35 commented Nov 5, 2024

CI in 1 seems to indicate that there are cases where the f16 infinite recursion bug (2, 3) can make its way into what gets called during tests, even though this doesn't seem to be the usual case. In order to make sure that we avoid these completely, just unset f16_enabled on any platforms that have the recursion problem.

This also refactors the match statement to be more in line with library/std/build.rs.

CI in [1] seems to indicate that there are cases where the `f16`
infinite recursion bug ([2], [3]) can make its way into what gets called
during tests, even though this doesn't seem to be the usual case. In
order to make sure that we avoid these completely, just unset
`f16_enabled` on any platforms that have the recursion problem.

This also refactors the `match` statement to be more in line with
`library/std/build.rs`.

[1]: rust-lang#729
[2]: llvm/llvm-project#97981
[3]: rust-lang#651
@tgross35
Copy link
Contributor Author

tgross35 commented Nov 5, 2024

@beetrees would you be able to review this?

Copy link
Contributor

@beetrees beetrees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tgross35 tgross35 merged commit a09218f into rust-lang:master Nov 5, 2024
26 checks passed
@tgross35 tgross35 deleted the f16-f128-config-update branch November 5, 2024 13:16
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.

2 participants