-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Fix type of get_tydesc intrinsic in typeck::check::check_intrinsic_type #3730
Labels
A-type-system
Area: Type system
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Comments
graydon
added a commit
to graydon/rust
that referenced
this issue
Feb 26, 2013
Not critical for 0.6, de-milestoning |
https://github.com/mozilla/rust/blob/incoming/src/librustc/front/intrinsic.rs#L21 pub fn get_tydesc<T>() -> *TyDesc {
unsafe {
rusti::get_tydesc::<T>() as *TyDesc
}
} This appears to be fixed, closing. |
I don't think this is closed. This look like the point of the issue is to get rid of the |
Closed
This has been fixed |
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Jul 29, 2024
Add `gettid` support Add support for `gettid` in miri. To ensure that the requirement that `getpid() == gettdi()` for the main thread, we use the value returned by `getpid` and add to it the internal thread index. Since `getpid` is only supported when isolation is disabled, and we want `gettid` to be used both in isolated and non-isolated executions, we modify `getpid` to return a hardcoded value (1000) when running in isolation mode. Fixes rust-lang#3730
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-type-system
Area: Type system
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Should be
*intrinsic::tydesc
and not*()
.The text was updated successfully, but these errors were encountered: