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

rustc: fix size computation of structs for the FFI #3716

Merged
merged 1 commit into from
Oct 17, 2012
Merged

rustc: fix size computation of structs for the FFI #3716

merged 1 commit into from
Oct 17, 2012

Conversation

Blei
Copy link
Contributor

@Blei Blei commented Oct 10, 2012

It didn't take alignment into account.

Fixes #3656.

It didn't take alignment into account.

Fixes #3656.
catamorphism added a commit that referenced this pull request Oct 17, 2012
rustc: fix size computation of structs for the FFI
@catamorphism catamorphism merged commit 7f12cc4 into rust-lang:incoming Oct 17, 2012
@catamorphism
Copy link
Contributor

Thanks!

RalfJung pushed a commit to RalfJung/rust that referenced this pull request Jun 29, 2024
…id_fixup-03, r=RalfJung

Remove GetCurrentProcessId's frame_in_std check

Most of the support required to close rust-lang#1727 was actually added a while back, in rust-lang#2215.

However, for some reason, even though the Unix/Linux syscall equivalent has no `frame_in_std()` check, the Windows `GetCurrentProcessId` check did. While the vast majority of use cases use `std::process::id`, there's no particular reason to penalize any Windows code that is no_std or for whatever other reason choses to call the function directly (e.g. via the generated [windows-sys](https://docs.rs/windows-sys/latest/windows_sys/Win32/System/Threading/fn.GetCurrentProcessId.html) method). The emulation should still work fine. Given there's no reason not to, we might as well simplify the code a tiny bit and save that branch / frame check during runtime too.

This PR removes the `frame_in_std` restriction for `GetCurrentProcessId`, and also moves it into the environment related shim section per discussion in rust-lang/miri#1727 (comment).

Still passes existing tests/pass/getpid.rs test.

Closes rust-lang#1727 unless we wish to give a dummy value when isolated, which we don't seem to want to do at this time.
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