Skip to content

Rollup of 8 pull requests #140165

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 20 commits into from
Apr 23, 2025
Merged

Rollup of 8 pull requests #140165

merged 20 commits into from
Apr 23, 2025

Conversation

ChrisDenton
Copy link
Member

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Berrysoft and others added 20 commits April 10, 2025 15:12
Extends the change from rust-lang#139653, which was on expressions, to literals.

Fixes rust-lang#140098.
…boet

Use posix_spawn on cygwin

r? ``@joboet``

Depends on:
- [x] rust-lang/libc#4387
- [x] rust-lang#140081
improve diagnostic for raw pointer field access with ->

This PR enhances the error messages emitted by the Rust compiler when users attempt to use the `->` operator for field access on raw pointers or when dereferencing is needed. The changes aim to provide clearer guidance, by suggesting the correct use of the `.` operator and explicit dereferencing.

**Before:**
```
help: `xs` is a raw pointer; try dereferencing it
   |
LL |         (*xs)->count += 1;
   |         ++  +
```

**Now:**
```
help: use `.` on a dereferenced raw pointer instead
   |
LL -         xs->count += 1;
LL +         (*xs).count += 1;
   |
```

I added extra clarification in the message. Since this error occurs in the parser, we can't be certain that the type is a raw pointer. That's why the message includes only a small note in brackets. (In contrast, the message above is emitted in HIR, where we *can* check whether it's a raw pointer.)

**Before:**
```
  --> main.rs:11:11
   |
11 |         xs->count += 1;
   |           ^^
   |
   = help: the . operator will dereference the value if needed
```
**After:**
```
--> main.rs:11:11
   |
11 |         xs->count += 1;
   |           ^^
   |
   = help: the `.` operator will automatically dereference the value, except if the value is a raw pointer
```
compiletest: Fix deadline bugs in new executor

The experimental new executor for compiletest (rust-lang#139660) was found to have two major bugs in deadline handling for detecting slow tests:

- The comparison between `now` and test deadlines was reversed, causing no timeouts to ever be recognised.
- After fixing that bug, it was found that the existing code would issue timeouts for any test that had started more than 60 seconds ago, even if the test had finished long before its deadline was reached.

This PR fixes those bugs.

(The new executor is not yet enabled by default, so this PR has no immediate effect on contributors.)

---

I noted in rust-lang#139998 (comment) that I hoped to have some unit tests to accompany these fixes. Unfortunately that turned out to be infeasible, because `DeadlineQueue` is tightly coupled to concrete `mpsc::Receiver` APIs (in addition to `Instant::now`), and trying to mock all of those would make the code much more complicated.

I did, however, add a few assertions that would have caught the failure to remove tests from the queue after their deadline.

r? jieyouxu
handle function alignment in miri

tracking issue: rust-lang#82232
Fixes rust-lang/miri#4282

The `#[repr(align(N))]` attribute on functions was ignored when using miri. For such a function, its address should be a multiple of `N`.

There is some further discussion in the thread [#t-compiler/const-eval > function address alignment](https://rust-lang.zulipchat.com/#narrow/channel/146212-t-compiler.2Fconst-eval/topic/function.20address.20alignment) on how `dyn Fn` should be handled. The behavior there appears to be consistent between miri and nightly, though both may be incorrect. In any case, that can be resolved separately.
…ils-on-impl-block, r=ZuseZ4

Fix auto diff failing on inherent impl blocks

closes: rust-lang#139557

r? ``@ZuseZ4``
Update books

## rust-lang/nomicon

1 commits in 0c10c30cc54736c5c194ce98c50e2de84eeb6e79..c76a20f0d987145dcedf05c5c073ce8d91f2e82a
2025-04-15 20:54:57 UTC to 2025-04-15 20:54:57 UTC

- Say that dereferencing a pointer to a ZST is no longer undefined (rust-lang/nomicon#467)

## rust-lang/reference

7 commits in 3340922df189bddcbaad17dc3927d51a76bcd5ed..3bf3402aea982b876eb56c87da17b0685c6461d5
2025-04-18 13:44:45 UTC to 2025-04-17 17:27:01 UTC

- Use `cfg(false)` instead of `cfg(FALSE)` (rust-lang/reference#1763)
-     Add `cfg(true)` and `cfg(false)` to conditional compilation (RFC 3695) (rust-lang/reference#1762)
- Refactor rendering with `RenderCtx` (rust-lang/reference#1796)
- attributes/codegen: update aarch64 features (rust-lang/reference#1791)
- Simplify GenericParams grammar (rust-lang/reference#1795)
- Add rule identifiers for the ABI chapter (rust-lang/reference#1793)
- Remove broken footnote links from grammar summary (rust-lang/reference#1794)
…nkov

Handle another negated literal in `eat_token_lit`.

Extends the change from rust-lang#139653, which was on expressions, to literals.

Fixes rust-lang#140098.

r? ``@petrochenkov``
test_nan: ensure the NAN contant is quiet

Follow-up to rust-lang#139483

r? ``@tgross35``
@rustbot rustbot added A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Apr 22, 2025
@ChrisDenton
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

📌 Commit 2d8264f has been approved by ChrisDenton

It is now in the queue for this repository.

@bors bors removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Apr 22, 2025
@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Apr 22, 2025
@bors
Copy link
Collaborator

bors commented Apr 22, 2025

⌛ Testing commit 2d8264f with merge 6a3a8b8...

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 22, 2025
…enton

Rollup of 8 pull requests

Successful merges:

 - rust-lang#139617 (Use posix_spawn on cygwin)
 - rust-lang#139921 (improve diagnostic for raw pointer field access with ->)
 - rust-lang#140031 (compiletest: Fix deadline bugs in new executor)
 - rust-lang#140072 (handle function alignment in miri)
 - rust-lang#140104 (Fix auto diff failing on inherent impl blocks)
 - rust-lang#140124 (Update books)
 - rust-lang#140144 (Handle another negated literal in `eat_token_lit`.)
 - rust-lang#140149 (test_nan: ensure the NAN contant is quiet)

r? `@ghost`
`@rustbot` modify labels: rollup
@rust-log-analyzer
Copy link
Collaborator

The job x86_64-mingw-1 failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
---- [run-make] tests\run-make\amdgpu-kd stdout ----

error: rmake recipe failed to complete
status: exit code: 1
command: "D:\\a\\rust\\rust\\build\\x86_64-pc-windows-gnu\\test\\run-make\\amdgpu-kd\\rmake.exe"
stdout: none
--- stderr -------------------------------
command failed at line 18
Command { cmd: "D:\\a\\rust\\rust\\build\\x86_64-pc-windows-gnu\\stage2\\bin\\rustc.exe" "-L" "D:\\a\\rust\\rust\\build\\x86_64-pc-windows-gnu\\test\\run-make\\amdgpu-kd\\rmake_out" "--crate-name" "foo" "--target=amdgcn-amd-amdhsa" "-Ctarget-cpu=gfx900" "--crate-type" "cdylib" "foo.rs", stdin_buf: None, stdin: None, stdout: None, stderr: None, drop_bomb: DropBomb { command: "D:\\a\\rust\\rust\\build\\x86_64-pc-windows-gnu\\stage2\\bin\\rustc.exe", defused: true, armed_location: Location { file: "D:\\a\\rust\\rust\\tests\\run-make\\amdgpu-kd\\rmake.rs", line: 12, col: 5 } }, already_executed: true }
output status: `exit code: 1`
=== STDOUT ===



=== STDERR ===
error: linking with `rust-lld` failed: exit code: 0xc0000374
  |
  = note: "rust-lld" "-flavor" "gnu" "--version-script=C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustcqdnP7f\\list" "--no-undefined-version" "<1 object files omitted>" "--as-needed" "-L" "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustcqdnP7f\\raw-dylibs" "-Bdynamic" "--eh-frame-hdr" "-z" "noexecstack" "-L" "D:\\a\\rust\\rust\\build\\x86_64-pc-windows-gnu\\test\\run-make\\amdgpu-kd\\rmake_out" "-o" "foo.elf" "--gc-sections" "-shared"
  = note: some arguments are omitted. use `--verbose` to show all linker arguments
  = note: 

error: aborting due to 1 previous error
------------------------------------------
---
test result: FAILED. 279 passed; 1 failed; 110 ignored; 0 measured; 6 filtered out; finished in 201.56s

Some tests failed in compiletest suite=run-make mode=run-make host=x86_64-pc-windows-gnu target=x86_64-pc-windows-gnu
Build completed unsuccessfully in 2:28:20
make: *** [Makefile:124: ci-mingw-x] Error 1
  local time: Tue Apr 22 20:40:51 CUT 2025
  network time: Tue, 22 Apr 2025 20:40:52 GMT
##[error]Process completed with exit code 2.
Post job cleanup.
[command]"C:\Program Files\Git\bin\git.exe" version

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Apr 22, 2025
@ChrisDenton
Copy link
Member Author

@bors retry spurious linking with rust-lld failed: exit code: 0xc0000374

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 22, 2025
@ChrisDenton ChrisDenton added A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) CI-spurious-fail-mingw CI spurious failure: target env mingw labels Apr 22, 2025
@bors
Copy link
Collaborator

bors commented Apr 22, 2025

⌛ Testing commit 2d8264f with merge 1a5bf12...

@bors
Copy link
Collaborator

bors commented Apr 23, 2025

☀️ Test successful - checks-actions
Approved by: ChrisDenton
Pushing 1a5bf12 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Apr 23, 2025
@bors bors merged commit 1a5bf12 into rust-lang:master Apr 23, 2025
7 checks passed
@rustbot rustbot added this to the 1.88.0 milestone Apr 23, 2025
Copy link

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 6bc57c6 (parent) -> 1a5bf12 (this PR)

Test differences

Show 33438 test diffs

Stage 1

  • ascii_char::test_display: [missing] -> pass (J0)
  • collections::binary_heap::test_drain: [missing] -> pass (J0)
  • collections::binary_heap::test_retain_catch_unwind: [missing] -> pass (J0)
  • collections::btree::map::tests::test_extract_if::height_0_keeping_one: [missing] -> pass (J0)
  • collections::hash::map::tests::test_show: [missing] -> pass (J0)
  • errors_with_multiple_writes_on_same_line_dont_insert_erroneous_newlines: [missing] -> pass (J0)
  • f32::test_log: [missing] -> pass (J0)
  • iter::adapters::flatten::test_flatten_non_fused_inner: [missing] -> pass (J0)
  • iter::range::test_range_from_take_collect: [missing] -> pass (J0)
  • iter::test_monad_laws_left_identity: [missing] -> pass (J0)
  • mem::offset_of_alias: [missing] -> pass (J0)
  • mem::uninit_write_clone_of_slice_panic_lt: [missing] -> pass (J0)
  • net::ip_addr::ipv6_const: [missing] -> pass (J0)
  • net::parser::parse_socket: [missing] -> pass (J0)
  • nonzero::nonzero_leading_zeros: [missing] -> pass (J0)
  • num::flt2dec::random::shortest_f32_exhaustive_equivalence_test: [missing] -> ignore (J0)
  • num::i32::test_rem_euclid: [missing] -> pass (J0)
  • num::test_try_isizei16: [missing] -> pass (J0)
  • num::test_try_u32i8: [missing] -> pass (J0)
  • num::u16::test_unbounded_shr: [missing] -> pass (J0)
  • option::option_const_mut: [missing] -> pass (J0)
  • ptr::thin_box: [missing] -> pass (J0)
  • slice::slice_index::rangeinclusive_exhausted::index_fail: [missing] -> pass (J0)
  • slice::test_chunks_next_back: [missing] -> pass (J0)
  • slice::test_ends_with: [missing] -> pass (J0)
  • slice::test_first: [missing] -> pass (J0)
  • sort::tests::stable::fixed_seed: [missing] -> pass (J0)
  • str::test_replacen: [missing] -> pass (J0)
  • str::test_rsplitn_char_iterator: [missing] -> pass (J0)
  • sort::tests::stable::correct_string_saw_mixed: [missing] -> ignore (J1)
  • sort::tests::unstable::stability_i32_random_s95: [missing] -> ignore (J1)
  • ascii::short::case08_fake_simd_u64: [missing] -> pass (J2)
  • iter::bench_flat_map_ref_sum: [missing] -> pass (J2)
  • linked_list::bench_iter_mut_rev: [missing] -> pass (J2)
  • num::int_log::u16_log_random_small: [missing] -> pass (J2)
  • process::tests::test_interior_nul_in_args_is_error: [missing] -> pass (J2)
  • slice::starts_with_diff_one_element_at_end: [missing] -> pass (J2)
  • sort::tests::stable::stability_i32_random_d20: [missing] -> pass (J2)
  • sort::tests::unstable::correct_1k_descending: [missing] -> pass (J2)
  • str::starts_with_ascii_char::short_ascii: [missing] -> pass (J2)
  • string::bench_from: [missing] -> pass (J2)
  • vec::test_try_reserve_exact: [missing] -> pass (J2)
  • back::rpath::tests::test_rpath_relative_issue_119571: [missing] -> pass (J3)
  • config::externs::tests::test_split_extern_opt: [missing] -> pass (J3)
  • errors::verify_codegen_ssa_expected_used_symbol_80: [missing] -> pass (J3)
  • errors::verify_codegen_ssa_rlib_incompatible_dependency_formats_43: [missing] -> pass (J3)
  • errors::verify_codegen_ssa_static_library_native_artifacts_to_file_62: [missing] -> pass (J3)
  • errors::verify_mir_build_static_in_pattern_0: [missing] -> pass (J3)
  • errors::verify_parse_pattern_method_param_without_body_48: [missing] -> pass (J3)
  • errors::verify_passes_unsupported_attributes_in_where_174: [missing] -> pass (J3)
  • errors::verify_resolve_anonymous_lifetime_non_gat_report_error_47: [missing] -> pass (J3)
  • errors::verify_resolve_cannot_find_builtin_macro_with_name_57: [missing] -> pass (J3)
  • errors::verify_resolve_macro_use_name_already_in_use_40: [missing] -> pass (J3)
  • spec::tests::arm_unknown_linux_gnueabihf: [missing] -> pass (J3)
  • spec::tests::powerpc_unknown_linux_gnu: [missing] -> pass (J3)

Stage 2

  • array::array_map: pass -> [missing] (J0)
  • ascii::test_is_ascii: pass -> [missing] (J0)
  • collections::binary_heap::test_push: pass -> [missing] (J0)
  • collections::linked_list::tests::test_clone_from: pass -> [missing] (J0)
  • fmt::formatting_options_flags: pass -> [missing] (J0)
  • io::buffered::tests::test_buffered_reader_seek: pass -> [missing] (J0)
  • iter::traits::iterator::test_min_by_key: pass -> [missing] (J0)
  • num::i128::test_next_multiple_of: pass -> [missing] (J0)
  • num::i32::test_rem_euclid: pass -> [missing] (J0)
  • num::u16::test_leading_trailing_ones: pass -> [missing] (J0)
  • num::u64::test_unbounded_shl: pass -> [missing] (J0)
  • pin_macro::extension_works_through_unsafe_block: pass -> [missing] (J0)
  • ptr::test_ptr_subtraction: pass -> [missing] (J0)
  • rc::test_clone: pass -> [missing] (J0)
  • sort::tests::stable::correct_i32_ascending: pass -> [missing] (J0)
  • sync::into_inner: pass -> [missing] (J0)
  • sort::tests::stable::correct_dyn_val_ascending: ignore -> [missing] (J1)
  • sort::tests::stable::self_cmp_cell_i32_descending: ignore -> [missing] (J1)
  • sort::tests::stable::self_cmp_cell_i32_random_d20: ignore -> [missing] (J1)
  • sort::tests::unstable::correct_1k_random_d2: ignore -> [missing] (J1)
  • sort::tests::unstable::correct_dyn_val_saw_mixed: ignore -> [missing] (J1)
  • sort::tests::unstable::stability_i32_descending: ignore -> [missing] (J1)
  • fs::tests::realpath_works_tricky: pass -> [missing] (J2)
  • slice::binary_search_l1_with_dups: pass -> [missing] (J2)
  • slice::sort_unstable_large_strings: pass -> [missing] (J2)
  • sort::tests::stable::correct_f128_saw_mixed: pass -> [missing] (J2)
  • sort::tests::unstable::observable_is_less_ascending: pass -> [missing] (J2)
  • str::char_count::emoji_huge::case03_manual_char_len: pass -> [missing] (J2)
  • str::char_count::emoji_tiny::case03_manual_char_len: pass -> [missing] (J2)
  • str::char_count::zh_small::case03_manual_char_len: pass -> [missing] (J2)
  • term::terminfo::parm::tests::test_basic_setabf: pass -> [missing] (J2)
  • errors::verify_ast_lowering_underscore_expr_lhs_assign_3: pass -> [missing] (J3)
  • errors::verify_codegen_ssa_self_contained_linker_missing_52: pass -> [missing] (J3)
  • errors::verify_codegen_ssa_unknown_atomic_ordering_86: pass -> [missing] (J3)
  • errors::verify_parse_in_in_typo_3: pass -> [missing] (J3)
  • errors::verify_passes_doc_inline_only_use_36: pass -> [missing] (J3)
  • errors::verify_passes_rustc_dirty_clean_69: pass -> [missing] (J3)
  • format_foreign::printf::tests::test_iter: pass -> [missing] (J3)
  • lints::verify_lint_builtin_unsafe_trait_9: pass -> [missing] (J3)
  • owned_slice::tests::static_storage: pass -> [missing] (J3)
  • parser::tests::span_of_self_arg_pat_idents_are_correct: pass -> [missing] (J3)
  • spec::tests::aarch64_be_unknown_linux_gnu: pass -> [missing] (J3)
  • spec::tests::aarch64_unknown_nto_qnx710: pass -> [missing] (J3)
  • spec::tests::i686_pc_windows_gnu: pass -> [missing] (J3)
  • sys::pal::unix::kernel_copy::tests::copy_specialization: pass -> [missing] (J4)

(and 16438 additional test diffs)

Additionally, 16900 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 1a5bf12f6586d724ed5ff40e58e06c0233560c0e --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. x86_64-apple-2: 1578.6s -> 4944.5s (213.2%)
  2. test-various: 2342.0s -> 4244.3s (81.2%)
  3. x86_64-apple-1: 5026.4s -> 8780.5s (74.7%)
  4. x86_64-gnu-aux: 4222.5s -> 6103.4s (44.5%)
  5. dist-aarch64-linux: 8529.2s -> 5261.4s (-38.3%)
  6. aarch64-apple: 3020.4s -> 3971.4s (31.5%)
  7. dist-x86_64-linux: 5585.5s -> 5018.4s (-10.2%)
  8. dist-apple-various: 5919.0s -> 6420.2s (8.5%)
  9. x86_64-gnu-distcheck: 4910.9s -> 4570.8s (-6.9%)
  10. dist-armhf-linux: 5307.3s -> 5005.9s (-5.7%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#139617 Use posix_spawn on cygwin d7edba88315413578b61075ac9bc77dfc7e701b6 (link)
#139921 improve diagnostic for raw pointer field access with -> 0027c6eab66541755ed23a773f41d744e5786efa (link)
#140031 compiletest: Fix deadline bugs in new executor fc957a1dc56df4b12dd7a299ec113319068227be (link)
#140072 handle function alignment in miri 0d298eac1e5ac6185ca9bae77325eb9cec8bf702 (link)
#140104 Fix auto diff failing on inherent impl blocks 9fca163b4a541e4438af1f7b362c96178b9d8e0a (link)
#140124 Update books e12d95b0df800f83ad766606e4d228211fb2400b (link)
#140144 Handle another negated literal in eat_token_lit. 3263f2970f261308e2c0948e7a20db9ec1f538ff (link)
#140149 test_nan: ensure the NAN contant is quiet d10696af517180b4e1c887e607d50bb678fd7fa2 (link)

previous master: 6bc57c6bf7

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (1a5bf12): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

mean range count
Regressions ❌
(primary)
0.2% [0.2%, 0.2%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.2% [-0.3%, -0.1%] 17
Improvements ✅
(secondary)
-0.3% [-0.6%, -0.2%] 48
All ❌✅ (primary) -0.2% [-0.3%, 0.2%] 18

Max RSS (memory usage)

Results (primary -1.3%, secondary -0.1%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
0.7% [0.7%, 0.7%] 1
Regressions ❌
(secondary)
6.4% [4.4%, 8.4%] 2
Improvements ✅
(primary)
-2.3% [-2.4%, -2.2%] 2
Improvements ✅
(secondary)
-2.2% [-2.6%, -1.8%] 6
All ❌✅ (primary) -1.3% [-2.4%, 0.7%] 3

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 774.196s -> 774.578s (0.05%)
Artifact size: 365.08 MiB -> 365.08 MiB (0.00%)

@jieyouxu jieyouxu added the CI-spurious-fail-rust-lld-crash CI spurious failure: `rust-lld` crashing / SIGSEGV / 0xc0000374 heap corruption label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-compiletest Area: The compiletest test runner A-spurious Area: Spurious failures in builds (spuriously == for no apparent reason) A-testsuite Area: The testsuite used to check the correctness of rustc CI-spurious-fail-mingw CI spurious failure: target env mingw CI-spurious-fail-rust-lld-crash CI spurious failure: `rust-lld` crashing / SIGSEGV / 0xc0000374 heap corruption merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.