- 07 11月, 2018 18 次提交
-
-
由 kennytm 提交于
Use trait impl method span when type param mismatch is due to impl Trait Fix #55374.
-
由 kennytm 提交于
Update lldb This updates lldb to pick up some bug fixes, and makes one minor test suite fix to account for this.
-
由 kennytm 提交于
Add `aarch64-pc-windows-msvc` to deployed targets Accidentally forgotten from #54718!
-
由 kennytm 提交于
-C remark: fix incorrect warning about requiring "--debuginfo" instead of "-C debuginfo=n" Previously suggested "--debuginfo" does not actually work.
-
由 kennytm 提交于
Standardised names and location of ui issue tests None
-
由 kennytm 提交于
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 #51947
-
由 kennytm 提交于
Fix feature gate only being checked on first repr attr. Reported in https://github.com/rust-lang/rust/issues/33158#issuecomment-412185357.
-
由 kennytm 提交于
Make `process_obligations`' computation of `completed` optional. It's only used in tests. This reduces instruction counts on several benchmarks by 0.5--1%.
-
由 kennytm 提交于
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.
-
由 kennytm 提交于
Choose predicates without inference variables over those with them Fixes #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.
-
由 kennytm 提交于
Remove unused re import in gdb_rust_pretty_printing
-
由 kennytm 提交于
Slight copy-editing for `std::cell::Cell` docs Hopefully this is a bit more precise and also more correct English.
-
由 bors 提交于
Change the ICE from #55223 to a hard error cc @SimonSapin r? @RalfJung fixes https://github.com/rust-lang/rust/issues/55287
-
由 Esteban Küber 提交于
-
由 bors 提交于
[CI] Run a `thumbv7m-none-eabi` binary using `qemu-system-arm` [IRR-2018-embedded] ## What's included? - Run a `thumbv7m-none-eabi` binary using `qemu-system-arm` - We are using `cortex-m-rt = "=0.5.4"` which does not use `proc_macro`. (reason: stage2 build of rustc does not work well with `proc_macro` in `run-make` phase.) - We are using GNU LD for now. ## Blocker All resolved. - ~[Waiting] `#[panic_handler]` is not available in stable.~ - [Merged] https://github.com/rust-lang/rust/pull/53619 - ~[Waiting] https://github.com/japaric/lm3s6965evb: does not compile on stable.~ - [OK] dependent crate ~`panic-abort`~ `panic-halt`: already moved to use `#[panic_handler]`. ## Update `#[panic_handler]` will be stabilized in Rust 1.30. CC @kennytm @jamesmunns @nerdyvaishali
-
由 Tom Tromey 提交于
This updates lldb to pick up some bug fixes, and makes one minor test suite fix to account for this.
-
由 Nikita Popov 提交于
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 #51947.
-
由 Felix S. Klock II 提交于
Add explcit `--error-format` options to tests of print-fuel to sidestep compiletests presumption of JSON. As a driveby, rename the stdout files to stderr, which should have been part of the earlier commit.
-
- 06 11月, 2018 22 次提交
-
-
由 bors 提交于
[breaking change] update stdsimd r? @alexcrichton
-
由 bors 提交于
Rollup of 11 pull requests Successful merges: - #55490 (resolve: Fix ICE in macro import error recovery) - #55597 (std: Enable usage of `thread_local!` through imports) - #55601 (Fix tracking issue numbers for some unstable features) - #55621 (Add precision for create_dir function) - #55644 (ci: Add Dockerfile for dist-powerpcspe-linux) - #55664 (Make "all possible cases" help message uniform with existing help messages) - #55689 (miri: binary_op_val -> binary_op_imm) - #55694 (Fixes #31076) - #55696 (NLL Diagnostic Review 3: Missing errors for borrows of union fields) - #55700 (Update ui tests with respect to NLL) - #55703 (Update `configure --help` (via configure.py) to reflect decoupling of debug+optimize)
-
由 kennytm 提交于
Update `configure --help` (via configure.py) to reflect decoupling of debug+optimize This should have been part of PR #54811 (my bad).
-
由 kennytm 提交于
Update ui tests with respect to NLL Fix #55533
-
由 kennytm 提交于
NLL Diagnostic Review 3: Missing errors for borrows of union fields Fixes #55675. This PR modifies a test to make it more robust (it also fixes indentation on a doc comment, but that's not the point of the PR). See the linked issue for details. r? @pnkfelix
-
由 kennytm 提交于
Fixes #31076
-
由 kennytm 提交于
miri: binary_op_val -> binary_op_imm Seems like this was overlooked during the value -> immediate rename. r? @oli-obk
-
由 kennytm 提交于
Make "all possible cases" help message uniform with existing help messages Specifically no capitalisation or trailing full stops.
-
由 kennytm 提交于
ci: Add Dockerfile for dist-powerpcspe-linux This adds the Dockerfile for cross-building Rust for the powerpcspe target. It's currently disabled.
-
由 kennytm 提交于
Add precision for create_dir function Took me a while to find the other equivalent so it seems to be necessary. r? @QuietMisdreavus
-
由 kennytm 提交于
Fix tracking issue numbers for some unstable features And also remove deprecated unstable `#[panic_implementation]` attribute that was superseded by stable `#[panic_handler]` and doesn't have an open tracking issue.
-
由 kennytm 提交于
std: Enable usage of `thread_local!` through imports The `thread_local!` macro delegated to an internal macro but it didn't do so in a macros-and-the-module-system compatible fashion, meaning if a `#![no_std]` crate imported `std` and tried to use `thread_local!` it would fail due to missing a lookup of an internal macro. This commit switches the macro to instead use `$crate` to invoke other macros, ensuring that it'll work when `thread_local!` is imported alone.
-
由 kennytm 提交于
resolve: Fix ICE in macro import error recovery Fixes https://github.com/rust-lang/rust/issues/55457
-
由 bors 提交于
std: Improve codegen size of accessing TLS Some code in the TLS implementation in libstd stores `Some(val)` into an `&mut Option<T>` (effectively) and then pulls out `&T`, but it currently uses `.unwrap()` which can codegen into a panic even though it can never panic. With sufficient optimizations enabled (like LTO) the compiler can see through this but this commit helps it along in normal mode (`--release` with Cargo by default) to avoid codegen'ing the panic path. This ends up improving the optimized codegen on wasm by ensuring that a call to panic pulling in more file size doesn't stick around.
-
由 Alexander Regueiro 提交于
-
由 bors 提交于
Use lld directly for Fuchsia target Fuchsia already uses lld as the default linker, so there's no reason to always invoke it through Clang, instead we can simply invoke lld directly and pass the set of flags that matches Clang.
-
由 Petr Hosek 提交于
Fuchsia already uses lld as the default linker, so there's no reason to always invoke it through Clang, instead we can simply invoke lld directly and pass the set of flags that matches Clang.
-
由 bors 提交于
Fix undefined behavior in Rc/Arc allocation Manually calculate allocation layout for `Rc`/`Arc` to avoid undefined behavior Closes #54908
-
由 bors 提交于
Correct alignment of atomic types and (re)add Atomic{I,U}128 This is a updated https://github.com/rust-lang/rust/pull/53514 to also make atomic types `repr(C)` as per comment in https://github.com/rust-lang/rust/pull/53514#issuecomment-431042767. Fixes #39590 Closes #53514 r? @pnkfelix
-
由 Murarth 提交于
Manually calculate allocation layout for `Rc`/`Arc` to avoid undefined behavior
-
由 Felix S. Klock II 提交于
-
由 Simonas Kazlauskas 提交于
-