- 28 8月, 2018 7 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
Less modes!
-
- 27 8月, 2018 10 次提交
-
-
由 bors 提交于
fix NLL ICEs Custom type-ops reuse some of the query machinery -- but while query results are canonicalized after they are constructed, custom type ops are not, and hence we have to resolve the type variables to avoid an ICE here. Also, use the type-op machinery for implied outlives bounds. Fixes #53568 Fixes #52992 Fixes #53680
-
由 bors 提交于
`HybridIdxSet` tweaks A couple of tweaks to `HybridIdxSet`. r? @nikomatsakis
-
由 bors 提交于
Move with_globals setup from run_compiler to run An alternative to https://github.com/rust-lang/rust/pull/53526 Note this breaks some miri stuff and clippy since they call `run_compiler` directly, and they now need to also call `with_globals ` cc @rust-lang/dev-tools r? @oli-obk
-
由 bors 提交于
change the default linker of the ARM Cortex-M targets to rust-lld so users won't need an external linker to build programs This will break nightly builds. We discussed this within the embedded WG and with the embedded community in rust-embedded/wg#160 and there was consensus in that this breaking change is worthwhile and that we should do it now before it becomes impossible to do without breaking stable builds. We have already written an announcement (see rust-embedded/wg#196) that explains the breakage and instructs the users how to fix their builds. The TL;DR is that they can switch to the old behavior by passing the `-C linker` flag to rustc. We'll post the announcement as soon as this change makes into nightly. closes rust-embedded/wg#160 r? @alexcrichton
-
由 John Kåre Alsaker 提交于
-
由 bors 提交于
rustc: Continue to tweak "std internal symbols" In investigating [an issue][1] with `panic_implementation` defined in an executable that's optimized I once again got to rethinking a bit about the `rustc_std_internal_symbol` attribute as well as weak lang items. We've sort of been non-stop tweaking these items ever since their inception, and this continues to the trend. The crux of the bug was that in the reachability we have a [different branch][2] for non-library builds which meant that weak lang items (and std internal symbols) weren't considered reachable, causing them to get eliminiated by ThinLTO passes. The fix was to basically tweak that branch to consider these symbols to ensure that they're propagated all the way to the linker. Along the way I've attempted to erode the distinction between std internal symbols and weak lang items by having weak lang items automatically configure fields of `CodegenFnAttrs`. That way most code no longer even considers weak lang items and they're simply considered normal functions with attributes about the ABI. In the end this fixes the final comment of #51342 [1]: https://github.com/rust-lang/rust/issues/51342#issuecomment-414368019 [2]: https://github.com/rust-lang/rust/blob/35bf1ae25799a4e62131159f052e0a3cbd27c960/src/librustc/middle/reachable.rs#L225-L238
-
由 John Kåre Alsaker 提交于
-
由 Alex Crichton 提交于
In investigating [an issue][1] with `panic_implementation` defined in an executable that's optimized I once again got to rethinking a bit about the `rustc_std_internal_symbol` attribute as well as weak lang items. We've sort of been non-stop tweaking these items ever since their inception, and this continues to the trend. The crux of the bug was that in the reachability we have a [different branch][2] for non-library builds which meant that weak lang items (and std internal symbols) weren't considered reachable, causing them to get eliminiated by ThinLTO passes. The fix was to basically tweak that branch to consider these symbols to ensure that they're propagated all the way to the linker. Along the way I've attempted to erode the distinction between std internal symbols and weak lang items by having weak lang items automatically configure fields of `CodegenFnAttrs`. That way most code no longer even considers weak lang items and they're simply considered normal functions with attributes about the ABI. In the end this fixes the final comment of #51342 [1]: https://github.com/rust-lang/rust/issues/51342#issuecomment-414368019 [2]: https://github.com/rust-lang/rust/blob/35bf1ae25799a4e62131159f052e0a3cbd27c960/src/librustc/middle/reachable.rs#L225-L238
-
由 bors 提交于
Include missing tools in the manifest and mark them as unavailable This PR changes the `build-manifest` tool to always include the missing components in the manifest, marking them as `available = false`. This blocks rustup from updating to a different nightly if the component is installed. The code builds and _should_ be correct, but I don't know a way to test the changes locally. r? @alexcrichton cc @kennytm https://github.com/rust-lang-nursery/rustup.rs/issues/1486
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #53043 (Improve unstable message display) - #53428 (libtest terse format: show how far in we are) - #53626 (Automatically expand a section even after page load) - #53651 (Add struct keyword doc) - #53706 (rustdoc: Fix gap on section anchor symbol when hovering.) Failed merges: - #53472 (Use FxHash{Map,Set} instead of the default Hash{Map,Set} everywhere in rustc.) r? @ghost
-
- 26 8月, 2018 16 次提交
-
-
由 Guillaume Gomez 提交于
rustdoc: Fix gap on section anchor symbol when hovering. Fixes #49485 for section headings.
-
由 Guillaume Gomez 提交于
Add struct keyword doc Slowly, one keyword at a time. r? @QuietMisdreavus
-
由 Guillaume Gomez 提交于
Automatically expand a section even after page load Fixes #52774
-
由 Guillaume Gomez 提交于
libtest terse format: show how far in we are So for example `./x.py test src/libcore` looks like ``` running 881 tests .................................................................................................... 100/881 .................................................................................................... 200/881 .................................................................................................... 300/881 .............................................................i.i.................................... 400/881 .................................................................................................... 500/881 .................................................................................................... 600/881 .................................................................................................... 700/881 .................................................................................................... 800/881 ................................................................................. test result: ok. 879 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out ``` When I am waiting for 3500 ui tests to complete, I am often missing some sense of how far in these 3500 it is. Getting the total count in `write_run_start` is a bit hacky; I did that to not change the "public interface" of the formatters. I can also give them an extra argument in their constructor so that they know from the beginning how many tests there will be. Would you prefer that? (I think I would, but I wanted to get feedback first.)
-
由 Guillaume Gomez 提交于
Improve unstable message display Fixes #51387. Reopening of #51563. New display: <img width="1440" alt="screen shot 2018-08-04 at 00 01 39" src="https://user-images.githubusercontent.com/3050060/43667793-dc14f708-9779-11e8-9808-f3ff126fc213.png"> r? @QuietMisdreavus
-
由 bors 提交于
Lazier sparse bit matrix A small NLL win. r? @nikomatsakis
-
由 bors 提交于
Update libc to include Fuchsia fixes cc https://github.com/rust-lang/libc/pull/1067, @sulanov r? @alexcrichton
-
由 bors 提交于
add #[panic_handler]; deprecate #[panic_implementation] r? @SimonSapin cc #44489
-
由 bors 提交于
Update Cargo submodule Also update Cargo's dependencies while we're at it
-
由 Alex Crichton 提交于
Also update Cargo's dependencies while we're at it
-
由 bors 提交于
Remove anonymous trait params from 2018 and beyond cc @Centril @nikomatsakis cc #41686 rust-lang/rfcs#2522 #53272 This PR removes support for anonymous trait parameters syntactically in rust 2018 and onward. TODO: - [x] Add tests
-
由 Pietro Albini 提交于
-
由 Eric Huss 提交于
Fixes #49485 for section headings.
-
由 bors 提交于
Update RLS Continuation of https://github.com/rust-lang/rust/pull/53610. Workspaces are tricky - the `json_internal` problem was only reproducible in Rust CI (not sure why it was only relevant to Windows?) and it seems that this was fixed by updating serde_json workspace-wide. Tested locally in Rust repo and it seems to be working. Nightlies are currently shipping without RLS, so it'd be great to include this in the next nightlies if possible.
-
由 Igor Matuszewski 提交于
This fixes 'cannot find macro `json_internal!` in this scope' RLS compilation error in Rust CI, presumably due to a local macro fix in serde_json 1.0.25 (https://github.com/serde-rs/json/commit/e40cbad70b39a0dd7975be8e5ad9018e2d45f791)
-
由 Igor Matuszewski 提交于
-
- 25 8月, 2018 7 次提交
-
-
由 bors 提交于
Fix #53525 - Unify E0243, E0244, E0087, E0088, E0089, and E0090 into E0107 Fix #53525 This pr merges all errors related to too many or too few generic arguments in types and functions. E0243, E0244, E0087, E0088, E0089, E0090 errors will no longer be emitted and E0107 will be used instead.
-
由 Kazuyoshi Kato 提交于
Doing the expansion on onhashchange seems too late. Fixes #48726
-
由 bors 提交于
Stablize Iterator::find_map Stabilization PR for https://github.com/rust-lang/rust/issues/49602
-
由 bors 提交于
Tidy CFTE/MIRI Fixes #53596
-
由 bors 提交于
Search a substring instead of start of string in rustdoc search Fixes #49762. r? @QuietMisdreavus
-
由 bors 提交于
MIR: support user-given type annotations on fns, structs, and enums This branch adds tooling to track user-given type annotations on functions, structs, and enum variant expressions. The user-given types are passed onto NLL which then enforces them. cc #47184 — not a complete fix, as there are more cases to cover r? @EddyB cc @rust-lang/wg-compiler-nll
-
由 Mark Mansi 提交于
-