Skip to content

[pull] swiftwasm-release/5.5 from release/5.5 #4144

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
merged 5 commits into from
Jan 22, 2022

Conversation

pull[bot]
Copy link

@pull pull bot commented Jan 22, 2022

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

compnerd and others added 5 commits January 20, 2022 18:02
This adjusts the Windows console to switch the codepage to UTF-8.  This
is important as the default codepage (CP437) does not allow for UTF-8
output, but expects ASCII.  However, strings in Swift are assumed to be
UTF-8, which means that there is now a conversion mismatch.

Because the console mode persists beyond the duration of the application
as it is state local to the console and not the C runtime, we should
restore the state of the console before termination.  We do this by
registering a termination handler via `atexit`.  This means that an
abnormal termination (e.g. via `fatalError`) will irrevocably alter the
state of the console (interestingly enough, `chcp` will still report the
original console codepage even though the console will internally be set
to UTF-8).

Fixes: SR-13807
(cherry picked from commit 9847cab)
Enable the test that was previously failing on 5.5.  This has been stable on main for a while, and seems to also be now passing on 5.5
[5.5] stdlib: change the console to UTF-8 on start
@MaxDesiatov MaxDesiatov enabled auto-merge January 22, 2022 07:59
@MaxDesiatov MaxDesiatov merged commit c0f1f02 into swiftwasm-release/5.5 Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants