-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 18 pull requests #74461
Rollup of 18 pull requests #74461
Conversation
Also adds some debug assertions to prevent API consumers from visiting those basic blocks by accident.
Might be subject to the birthday paradox occasionally, causing spurious failures. Addresses: rust-lang#70740 (review)
This is no longer used since rust-lang#63649
Needed to support rust-lang/project-rfc-2229#7 Currently rustc_typeck depends on rustc_middle for definition TypeckTables, etc. For supporting project-rfc-2229#7, rustc_middle would've to depend on rustc_typeck for Place -- introducing a circular dependcy. This resembles the MIR equivalent of `Place` located in `lbrustc_middle/mir`. Co-authored-by: Aman Arora <me@aman-arora.com> Co-authored-by: Jennifer Wills <wills.jenniferg@gmail.com> Co-authored-by: Logan Mosier <logmosier@gmail.com>
Because the old one is harder to read and confuse typing checkers.
As a none-native speaker I stumbled upon this, looked it up and couldn't find a phrase, so I made my own assumption that "in any way" was meant (which is the meaning I would've deduced anyway)
`rustc` allows passing in predefined target triples as well as JSON target specification files. This change allows bootstrap to have the first inkling about those differences. This allows building a cross-compiler for an out-of-tree architecture (even though that compiler won't work for other reasons). Even if no one ever uses this functionality, I think the newtype around the `Interned<String>` improves the readability of the code.
Fix src/test/run-make/static-pie/test-aslr.rs Might be subject to the birthday paradox occasionally, causing spurious failures. Addresses: rust-lang#70740 (review)
Use intra-doc links in core::iter module This will make core::iter doc depend less on std doc.
add lazy normalization regression tests We previously didn't have simple tests which fail if we aren't careful around lazy normalization. We now do.
…rk-Simulacrum Add CSS tidy check r? @Mark-Simulacrum
…r=spastorino Remove leftover from emscripten fastcomp support This is no longer used since rust-lang#63649
…hewjasper Don't assign `()` to `!` MIR locals Implements the fix described in rust-lang#73860 (comment). Fixes rust-lang#73860 r? @matthewjasper
…i-obk Use an UTF-8 locale for the linker. Using a `C` locale breaks unicode filenames on Guix, where the linker is wrapped by a Guile program.
…atsakis Move hir::Place to librustc_middle/hir Needed to support rust-lang/project-rfc-2229#7 Currently rustc_typeck depends on rustc_middle for definition TypeckTables, etc. For supporting project-rfc-2229#7, rustc_middle would've to depend on rustc_typeck for Place -- introducing a circular dependency. This resembles the MIR equivalent of `Place` located in `lbrustc_middle/mir`. Separate PR for this move will make the actual PR for using Places to represent captures cleaner/more focused. r? @nikomatsakis @matthewjasper
…onas-schievink docs: better demonstrate that None values are skipped as many times a… …s needed
warn about uninitialized multi-variant enums Fixes rust-lang#73608
Fix Arc::as_ptr docs As a non-native speaker I stumbled upon this, looked it up and couldn't find a phrase, so I made my own assumption that "in any way" was meant (which is the meaning I would've deduced anyway)
intra-doc links: resolve modules in the type namespace Fixes rust-lang#62830 Modules actually live in the type namespace, not all three, and it's not possible to clash a type with a module.
📌 Commit c587386 has been approved by |
@bors treeclosed=5 I'm around |
☀️ Test successful - checks-actions, checks-azure |
Looks like something in here had quite the perf impact https://perf.rust-lang.org/compare.html?start=39d5a61f2e4e237123837f5162cc275c2fd7e625&end=d3df8512d2c2afc6d2e7d8b5b951dd7f2ad77b02&stat=instructions:u |
There are a couple MIR changes, maybe those? |
Oh and because of the revert was tested, we can measure the impact of this rollup without the big linker regression: https://perf.rust-lang.org/compare.html?start=39d5a61f2e4e237123837f5162cc275c2fd7e625&end=556b0eb41b4273f0dcde2cbc2bc9f53e2c09d688 |
Those results shows that the linker regression caused all of the regression. With it removed, the remaining 17 PRs actually gave some small wins, except for two unimportant exceptions:
So, I think we are done here! Thanks to @Mark-Simulacrum and @eddyb for their efforts on this. |
Successful merges:
run-make-fulldeps
tests #74009 (Fix MinGWrun-make-fulldeps
tests)()
to!
MIR locals #74411 (Don't assign()
to!
MIR locals)Failed merges:
r? @ghost