-
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
Rollup of 8 pull requests #113105
Rollup of 8 pull requests #113105
Conversation
These are LLVM target features which allow the `smc` and `hvc` instructions respectively to be used in inline assembly.
Add trustzone and virtualization target features for aarch32. These are LLVM target features which allow the `smc` and `hvc` instructions respectively to be used in inline assembly.
…inking, r=davidtwco Make compiletest aware of targets without dynamic linking Some parts of the compiletest internals and some tests require dynamic linking to work, which is not supported by all targets. Before this PR, this was handled by if branches matching on the target name. This PR loads whether a target supports dynamic linking or not from the target spec, and adds a `// needs-dynamic-linking` attribute for tests that require it. Note that I was not able to replace all the old conditions based on the target name, as some targets have `dynamic_linking: true` in their spec but pretend they don't have it in compiletest. Also, to get this to work I had to *partially* revert rust-lang#111472 (cc `@djkoloski` `@tmandry` `@bjorn3).` On one hand, only the target spec contains whether a target supports dynamic linking, but on the other hand a subset of the fields can be overridden through `-C` flags (as far as I'm aware only `-C panic=$strategy`). The solution I came up with is to take the target spec as the base, and then override the panic strategy based on `--print=cfg`. Hopefully that should not break y'all again.
…shtriplett Allow comparing `Box`es with different allocators Currently, comparing `Box`es over different allocators is not allowed: ```Rust error[E0308]: mismatched types --> library/alloc/tests/boxed.rs:22:20 | 22 | assert_eq!(b1, b2); | ^^ expected `Box<{integer}, ConstAllocator>`, found `Box<{integer}, AnotherAllocator>` | = note: expected struct `Box<{integer}, ConstAllocator>` found struct `Box<{integer}, AnotherAllocator>` For more information about this error, try `rustc --explain E0308`. error: could not compile `alloc` (test "collectionstests") due to previous error ``` This PR lifts this limitation
…le-options, r=davidtwco Provide more context for `rustc +nightly -Zunstable-options` on stable <img width="724" alt="Screenshot 2023-06-16 123456" src="https://github.com/rust-lang/rust/assets/39484203/1933e172-cb9f-4e51-9540-ade803a88360"> Closes rust-lang#110090.
Make `UnwindAction::Continue` explicit in MIR dump Makes it easier to spot unwinding related issues in MIR by making `UnwindAction::Continue` explicit, just like all other `UnwindAction`s.
…a-obj-unless-denied, r=compiler-errors Add tests impl via obj unless denied Fixes rust-lang#112737 Add simple tests to check feature change in rust-lang#112320 is performing as expected. Note: - Unsure about filenames, locations & function signature names (tried to make them something sensible)
Simplify some conditions r? `@Nilstrieb` Some things taken out of my `is_none_or` pr.
…mpiler-errors Normalize types when applying uninhabited predicate. Fixes rust-lang#112997
@bors r+ rollup=never p=8 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 5ea6668646 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (6b46c99): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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.
CyclesResultsThis 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 661.601s -> 662.939s (0.20%) |
Successful merges:
Box
es with different allocators #112628 (Allow comparingBox
es with different allocators)rustc +nightly -Zunstable-options
on stable #112692 (Provide more context forrustc +nightly -Zunstable-options
on stable)UnwindAction::Continue
explicit in MIR dump #112972 (MakeUnwindAction::Continue
explicit in MIR dump)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup