Skip to content

test: guard part of stdlib/StaticBigInt.swift for 32-bit at compile-time #62782

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

Conversation

kateinoigakukun
Copy link
Member

To avoid integer literal overflows at compile-time

@benrimmington
Copy link
Contributor

Thanks. This will be fixed by #62746 when the branch is unlocked.
Swift CI no longer uses the watchsimulator-i386 target.
Can it use a wasm32 target to detect this kind of issue, or is that only available externally?

@kateinoigakukun
Copy link
Member Author

Ah, I overlooked it. Thanks.
Unfortunately, wasm32 ci is still only available on our fork. We are continuously trying upstreaming patches to make it possible.

@kateinoigakukun kateinoigakukun deleted the pr-817153a2b4cbedb92c9e325db00db1ee079ac0d2 branch December 29, 2022 11:03
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