-
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 14 pull requests #55746
Rollup of 14 pull requests #55746
Conversation
Hopefully this is a bit more precise and also more correct English.
Fixes rust-lang#54705 When constructing synthetic auto trait impls, we may come across multiple predicates involving the same type, trait, and substitutions. Since we can only display one of these, we pick the one with the 'most strict' lifetime paramters. This ensures that the impl we render the user is actually valid (that is, a struct matching that impl will actually implement the auto trait in question). This commit exapnds the definition of 'more strict' to take into account inference variables. We always choose a predicate without inference variables over a predicate with inference variables.
Rustbuild passes `--message-format json` to the compiler invocations which causes JSON to be emitted on stdout. Printing optimization fuel messages to stdout breaks the json and causes Rustbuild to fail. Work around this by emitting optimization fuel related messages on stderr instead.
It's only used in tests. This reduces instruction counts on several benchmarks by 0.5--1%.
…d of "-C debuginfo=n"
Accidentally forgotten from rust-lang#54718!
…ep compiletests presumption of JSON. As a driveby, rename the stdout files to stderr, which should have been part of the earlier commit.
If we're going to emit bitcode (through ThinLTOBuffer), then we need to ensure that anon globals are named. This was already done after optimization passes, but also has to happen after LTO passes, as we always emit the final result in a ThinLTO-compatible manner. Fixes rust-lang#51947.
This updates lldb to pick up some bug fixes, and makes one minor test suite fix to account for this.
Slight copy-editing for `std::cell::Cell` docs Hopefully this is a bit more precise and also more correct English.
Remove unused re import in gdb_rust_pretty_printing
…nkfelix Choose predicates without inference variables over those with them Fixes rust-lang#54705 When constructing synthetic auto trait impls, we may come across multiple predicates involving the same type, trait, and substitutions. Since we can only display one of these, we pick the one with the 'most strict' lifetime paramters. This ensures that the impl we render the user is actually valid (that is, a struct matching that impl will actually implement the auto trait in question). This commit exapnds the definition of 'more strict' to take into account inference variables. We always choose a predicate without inference variables over a predicate with inference variables.
…ikomatsakis Don't print opt fuel messages to stdout because it breaks Rustbuild Rustbuild passes `--message-format json` to the compiler invocations which causes JSON to be emitted on stdout. Printing optimization fuel messages to stdout breaks the json and causes Rustbuild to fail. Work around this by emitting optimization fuel related messages on stderr instead.
Make `process_obligations`' computation of `completed` optional. It's only used in tests. This reduces instruction counts on several benchmarks by 0.5--1%.
…=petrochenkov Fix feature gate only being checked on first repr attr. Reported in rust-lang#33158 (comment).
Run name-anon-globals after LTO passes as well If we're going to emit bitcode (through ThinLTOBuffer), then we need to ensure that anon globals are named. This was already done after optimization passes, but also has to happen after LTO passes, as we always emit the final result in a ThinLTO-compatible manner. I added the test as `run-make`. The important bit is that we emit bitcode in some way (e.g. `--crate-type rlib` or `--emit=llvm-bc`). Please tell me if there is a better way to test for that. Fixes rust-lang#51947
Standardised names and location of ui issue tests None
… r=michaelwoerister -C remark: fix incorrect warning about requiring "--debuginfo" instead of "-C debuginfo=n" Previously suggested "--debuginfo" does not actually work.
…ichaelwoerister Add `aarch64-pc-windows-msvc` to deployed targets Accidentally forgotten from rust-lang#54718!
@bors r+ p=15 |
📌 Commit 79cf95ba51a035309e6c258e9e35ef3585050ada has been approved by |
⌛ Testing commit 79cf95ba51a035309e6c258e9e35ef3585050ada with merge a8d2cd8203f90c0e6de438d9d4de6392f2f98800... |
💔 Test failed - status-travis |
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 |
Update lldb This updates lldb to pick up some bug fixes, and makes one minor test suite fix to account for this.
…=varkor Use trait impl method span when type param mismatch is due to impl Trait Fix rust-lang#55374.
refactor: use shorthand fields refactor: use shorthand for single fields everywhere (excluding tests).
…r=oli-obk do not print wrapping ranges like normal ranges in validity diagnostics
📌 Commit 4e86576 has been approved by |
Rollup of 14 pull requests Successful merges: - #55377 (Slight copy-editing for `std::cell::Cell` docs) - #55441 (Remove unused re import in gdb_rust_pretty_printing) - #55453 (Choose predicates without inference variables over those with them) - #55495 (Don't print opt fuel messages to stdout because it breaks Rustbuild) - #55501 (Make `process_obligations`' computation of `completed` optional.) - #55510 (Fix feature gate only being checked on first repr attr.) - #55609 (Run name-anon-globals after LTO passes as well) - #55645 (do not print wrapping ranges like normal ranges in validity diagnostics) - #55688 (Standardised names and location of ui issue tests) - #55692 (-C remark: fix incorrect warning about requiring "--debuginfo" instead of "-C debuginfo=n") - #55702 (Add `aarch64-pc-windows-msvc` to deployed targets) - #55728 (Update lldb) - #55730 (Use trait impl method span when type param mismatch is due to impl Trait) - #55734 (refactor: use shorthand fields)
☀️ Test successful - status-appveyor, status-travis |
Rollup of 14 pull requests Successful merges: - rust-lang#55377 (Slight copy-editing for `std::cell::Cell` docs) - rust-lang#55441 (Remove unused re import in gdb_rust_pretty_printing) - rust-lang#55453 (Choose predicates without inference variables over those with them) - rust-lang#55495 (Don't print opt fuel messages to stdout because it breaks Rustbuild) - rust-lang#55501 (Make `process_obligations`' computation of `completed` optional.) - rust-lang#55510 (Fix feature gate only being checked on first repr attr.) - rust-lang#55609 (Run name-anon-globals after LTO passes as well) - rust-lang#55645 (do not print wrapping ranges like normal ranges in validity diagnostics) - rust-lang#55688 (Standardised names and location of ui issue tests) - rust-lang#55692 (-C remark: fix incorrect warning about requiring "--debuginfo" instead of "-C debuginfo=n") - rust-lang#55702 (Add `aarch64-pc-windows-msvc` to deployed targets) - rust-lang#55728 (Update lldb) - rust-lang#55730 (Use trait impl method span when type param mismatch is due to impl Trait) - rust-lang#55734 (refactor: use shorthand fields)
Successful merges:
std::cell::Cell
docs #55377 (Slight copy-editing forstd::cell::Cell
docs)process_obligations
' computation ofcompleted
optional. #55501 (Makeprocess_obligations
' computation ofcompleted
optional.)aarch64-pc-windows-msvc
to deployed targets #55702 (Addaarch64-pc-windows-msvc
to deployed targets)