-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rollup of 4 pull requests #68384
Rollup of 4 pull requests #68384
Conversation
This PR complements rust-lang#68253
The `layout` for the returned allocation of a `realloc` is only implicitly specified. This change makes it explicit.
Fix #[track_caller] and function pointers Starting with failing tests, fix the miscompilation and ICE caused by `ReifyShim` bug. Fixes rust-lang#68178.
AArch64 bare-metal targets: Build rust-std This PR complements rust-lang#68253
Add `riscv64gc-unknown-linux-gnu` into target list in build-manifest Missed in rust-lang#68037 r? @alexcrichton
Added minor clarification to specification of GlobalAlloc::realloc. The specification of `realloc` is slightly unclear: ``` /// * `layout` must be the same layout that was used /// to allocate that block of memory, ``` https://github.com/rust-lang/rust/blob/master/src/libcore/alloc.rs#L541-L542 In the case of an `alloc` or `alloc_zeroed` this is fairly evidently the `layout` parameter passed into the original call. In the case of a `realloc`, this I assume is `layout` modified to contain `new_size`. However, I could not find this case specified in the documentation. Thus technically in a sequence of calls to `realloc`, it would be valid to provide the second call to `realloc` the same `layout` as the first call to `realloc`, which is almost certainly not going to be handled correctly. This PR attempts to clarify the specification.
@bors r+ p=4 rollup=never |
📌 Commit 6b214b1 has been approved by |
⌛ Testing commit 6b214b1 with merge 5f73040c05f3c7965702e92141c1afd7f2ebddfe... |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
💔 Test failed - checks-azure |
Commented on the PR that seems to be the cause, closing. |
Successful merges:
riscv64gc-unknown-linux-gnu
into target list in build-manifest #68339 (Addriscv64gc-unknown-linux-gnu
into target list in build-manifest)Failed merges:
r? @ghost