-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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 12 pull requests #75510
Rollup of 12 pull requests #75510
Commits on Jul 22, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 9b5a974 - Browse repository at this point
Copy the full SHA 9b5a974View commit details
Commits on Aug 9, 2020
-
Fix ICE rust-lang#75307 in
format
Remove usages of `unwrap` (even when some are safe today).
Configuration menu - View commit details
-
Copy full SHA for 0a4f4e8 - Browse repository at this point
Copy the full SHA 0a4f4e8View commit details
Commits on Aug 11, 2020
-
Revert "Suppress debuginfo on naked function arguments"
This reverts commit 2567074. This commit does not actually fix the problem. It merely removes the name of the argument from the LLVM output. Even without the name, Rust codegen still spills the (nameless) variable onto the stack which is the root cause. The root cause is solved in the next commit.
Configuration menu - View commit details
-
Copy full SHA for 0356bb9 - Browse repository at this point
Copy the full SHA 0356bb9View commit details -
Don't spill operands onto the stack in naked functions
Currently, the code spills operands onto the stack for the purpose of debuginfo. However, naked functions can only contain an asm block. Therefore, attempting to spill the operands on the stack is undefined behavior. Fixes rust-lang#42779 cc rust-lang#32408
Configuration menu - View commit details
-
Copy full SHA for 050fb38 - Browse repository at this point
Copy the full SHA 050fb38View commit details
Commits on Aug 12, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 0e26f9b - Browse repository at this point
Copy the full SHA 0e26f9bView commit details -
Configuration menu - View commit details
-
Copy full SHA for bff104d - Browse repository at this point
Copy the full SHA bff104dView commit details -
Configuration menu - View commit details
-
Copy full SHA for b38e571 - Browse repository at this point
Copy the full SHA b38e571View commit details -
Change registered "program name" for -Cllvm-args usage messages
While debugging a codegen issue, I tried adding LLVM options with the rustc -Cllvm-args option, and was confused by the error and usage messaging. The LLVM "program name" argument is set to "rustc", and command line error messages make it look like invalid arguments are "rustc" arguments, not LLVM. I changed this argument so error messages and the "-help" usage feedback is easier to understand and react to. (Clang does something similar.)
Configuration menu - View commit details
-
Copy full SHA for d4593af - Browse repository at this point
Copy the full SHA d4593afView commit details
Commits on Aug 13, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 2100e67 - Browse repository at this point
Copy the full SHA 2100e67View commit details -
Configuration menu - View commit details
-
Copy full SHA for 08d9517 - Browse repository at this point
Copy the full SHA 08d9517View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2338903 - Browse repository at this point
Copy the full SHA 2338903View commit details -
Configuration menu - View commit details
-
Copy full SHA for 264434f - Browse repository at this point
Copy the full SHA 264434fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9302c17 - Browse repository at this point
Copy the full SHA 9302c17View commit details
Commits on Aug 14, 2020
-
Rollup merge of rust-lang#74650 - estebank:ambiguous-expr-binop, r=eddyb
Correctly parse `{} && false` in tail expression Fix rust-lang#74233, fix rust-lang#54186.
Configuration menu - View commit details
-
Copy full SHA for 5b5eec7 - Browse repository at this point
Copy the full SHA 5b5eec7View commit details -
Rollup merge of rust-lang#75319 - estebank:format-ice, r=eddyb
Fix ICE rust-lang#75307 in `format` Remove usages of `unwrap` (even when some are safe today). Fix rust-lang#75307.
Configuration menu - View commit details
-
Copy full SHA for 8c361aa - Browse repository at this point
Copy the full SHA 8c361aaView commit details -
Rollup merge of rust-lang#75417 - npmccallum:naked, r=matthewjasper
Don't spill operands onto the stack in naked functions Currently, the code spills operands onto the stack for the purpose of debuginfo. However, naked functions can only contain an asm block. Therefore, attempting to spill the operands on the stack is undefined behavior. Fixes rust-lang#42779 cc rust-lang#32408 Note that this PR reverts rust-lang#74105 which ultimately didn't fix the problem. cc @haraldh @Amanieu @matthewjasper
Configuration menu - View commit details
-
Copy full SHA for 1f73e89 - Browse repository at this point
Copy the full SHA 1f73e89View commit details -
Rollup merge of rust-lang#75452 - michaelwoerister:sp-cache-more-quer…
…y-keys, r=lcnr self-profile: Cache more query key strings when doing self-profiling. This PR adds optimized `SpecIntoSelfProfilingString` implementations for two common query key types (`LocalDefId` and `WithOptConstParam`). This makes raw self-profiling data on disk 8-9% smaller for my two test cases (`regex` and `cargo`). The on-disk format is not affected, so no tooling updates need to happen. I also tried adding an impl for `Ty<'tcx>` (which should reduce size quite a bit) but the compiler did not allow me to add a specialized impl parameterized with `'tcx`. I don't know if there is an actual problem with that or if the implementation of specialization just doesn't support it yet. cc @wesleywiser @Mark-Simulacrum
Configuration menu - View commit details
-
Copy full SHA for 6f964f0 - Browse repository at this point
Copy the full SHA 6f964f0View commit details -
Rollup merge of rust-lang#75459 - RalfJung:local-info, r=oli-obk
fix LocalInfo doc comment The doc comment makes it sound like this is diagnostics-only, but that is not true -- even [unsafety checking uses this information](https://github.com/rust-lang/rust/blob/ded20c98be8585b2a9fe4eeadd1be5524f6ffb17/src/librustc_mir/transform/check_unsafety.rs#L206), so it is crucial for soundness, not just "nice to have". Cc @oli-obk
Configuration menu - View commit details
-
Copy full SHA for c76259a - Browse repository at this point
Copy the full SHA c76259aView commit details -
Rollup merge of rust-lang#75462 - Mark-Simulacrum:clean-queries, r=pe…
…trochenkov Remove unused tcx parameter We shouldn't need access to a query context when storing already computed values.
Configuration menu - View commit details
-
Copy full SHA for 84f7991 - Browse repository at this point
Copy the full SHA 84f7991View commit details -
Rollup merge of rust-lang#75467 - rubenrua:rubenrua-patch-E0477, r=ol…
…i-obk Fix E0741 error code explanation Using `ok !` into fixed SRC like in other explanations.
Configuration menu - View commit details
-
Copy full SHA for b4966a8 - Browse repository at this point
Copy the full SHA b4966a8View commit details -
Rollup merge of rust-lang#75471 - richkadel:llvm-program-name, r=wesl…
…eywiser Change registered "program name" for -Cllvm-args usage messages While debugging a codegen issue, I tried adding LLVM options with the rustc -Cllvm-args option, and was confused by the error and usage messaging. The LLVM "program name" argument is set to "rustc", and command line error messages make it look like invalid arguments are "rustc" arguments, not LLVM. I changed this argument so error messages and the "-help" usage feedback is easier to understand and react to. (Clang does something similar.) r? @wesleywiser
Configuration menu - View commit details
-
Copy full SHA for d000fb1 - Browse repository at this point
Copy the full SHA d000fb1View commit details -
Rollup merge of rust-lang#75477 - RalfJung:fn-ptrs, r=Mark-Simulacrum
Expand function pointer docs Be more explicit in the ABI section, and add a section on how to obtain a function pointer, which can be somewhat confusing. Cc rust-lang#75239
Configuration menu - View commit details
-
Copy full SHA for 33fca5a - Browse repository at this point
Copy the full SHA 33fca5aView commit details -
Rollup merge of rust-lang#75479 - matthiaskrgr:package_docs, r=Mark-S…
…imulacrum make rustc-docs component available to rustup The `rustc-docs` component was generated but not selectable via rustup. Zulip thread: https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/rustc.20nightly.20docs.20as.20component.3F r? @Mark-Simulacrum
Configuration menu - View commit details
-
Copy full SHA for 9cbc031 - Browse repository at this point
Copy the full SHA 9cbc031View commit details -
Rollup merge of rust-lang#75496 - spastorino:prioritization-zulip-top…
…ics, r=Mark-Simulacrum Prioritization WG: Open Zulip topics only for `I-prioritize` issues This was discussed in https://rust-lang.zulipchat.com/#narrow/stream/227806-t-compiler.2Fwg-prioritization/topic/nominations.20and.20other.20automatically.20opened.20topics Is not being helpful to open topics on any of these events and it's even causing more work for the group. @LeSeulArtichaut ... I think this is all that's needed to get rid of this, right?. r? @Mark-Simulacrum cc @rust-lang/wg-prioritization @bors rollup=always
Configuration menu - View commit details
-
Copy full SHA for 912b5b3 - Browse repository at this point
Copy the full SHA 912b5b3View commit details -
Rollup merge of rust-lang#75500 - glandium:arm64-mac-zlib, r=Mark-Sim…
…ulacrum Disable zlib in LLVM on aarch64-apple-darwin For some reason, building rustc on the Apple Silicon DTK fails with some undefined symbols from zlib, which I guess is similar to some issues that appeared on *-apple-ios and *-apple-tvos.
Configuration menu - View commit details
-
Copy full SHA for e8acafd - Browse repository at this point
Copy the full SHA e8acafdView commit details