Never MIR inline functions with a different instruction set#81753
Never MIR inline functions with a different instruction set#81753bors merged 1 commit intorust-lang:masterfrom
Conversation
|
Do you think adding a mir-opt test would be worth it, given that running it |
|
hmm... yea, the difficulty of updating the test seems to me like a too high cost for the gain of a fairly straight forward test @bors r+ rollup |
|
📌 Commit 14ce0e861427cc1c73ea47c06ef61585a6e52720 has been approved by |
|
Is this required for soundness? If so, I think we should definitely add a test. |
|
@bors r- yes it's required for soundness... |
14ce0e8 to
41d51ad
Compare
|
The job Click to see the possible cause of the failure (guessed by this bot) |
41d51ad to
eb5e2d0
Compare
|
Added a |
|
@bors r+ holy 🐮 I guess we should make more use of |
|
📌 Commit eb5e2d0 has been approved by |
Rollup of 7 pull requests Successful merges: - rust-lang#80011 (Stabilize `peekable_next_if`) - rust-lang#81580 (Document how `MaybeUninit<Struct>` can be initialized.) - rust-lang#81610 (BTreeMap: make Ord bound explicit, compile-test its absence) - rust-lang#81664 (Avoid a hir access inside get_static) - rust-lang#81675 (Make rustdoc respect `--error-format short` in doctests) - rust-lang#81753 (Never MIR inline functions with a different instruction set) - rust-lang#81795 (Small refactor with Iterator::reduce) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
No description provided.