| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
`make::match_arm` should take a single `ast::Pat`, and callers can handle creating an `ast::OrPat` if need be. It should also take a proper `ast::MatchGuard`, instead of making one itself.
|
|
`expr_unit` is just a shortcut for a common expression, so it belongs in `make::ext`
|
|
|
|
|
|
|
|
`Into<ast::Expr>`
This will help with specializing the various `make::expr_*` functions later
|
|
|
|
Before this commit, replace-version-placeholder hardcoded the path
defining CURRENT_RUSTC_VERSION (to avoid replacing it). After a refactor
moved the file defining it without changing the hardcoded path, the tool
started replacing the constant itself with the version number.
To avoid this from happening in the future, this changes the definition
of the constant to avoid the tool from ever matching it.
|
|
We ignore `#[test]` in the def map, so that's why it failed.
|
|
r=jieyouxu,GuillaumeGomez
Move the has_errors check in rustdoc back to after TyCtxt is created
This was accidentally moved before TyCtxt creation by https://github.com/rust-lang/rust/pull/134302.
|
|
chore: remove redundant words in comment
|
|
Don't enable anyhow's `backtrace` feature in opt-dist
As of the stabilization of `std::backtrace` in Rust 1.65, this package flag has no effect other than to enable an unused dependency on the `backtrace` crate.
(See <https://github.com/dtolnay/anyhow/blob/af0937ef72fbaf9784a6c991e029738728d025e2/Cargo.toml#L18-L23>.)
While the presence of this feature in opt-dist doesn't cause other tools (which use anyhow) to actually *build* backtrace, it does affect the global crate graph used for dependency version resolution. After removing this feature, we can use `cargo tree --invert --package backtrace` to see that the only remaining reverse-dependency of backtrace is `color-eyre`, which is used by `ui_test`.
|
|
bootstrap: Consolidate coverage test suite steps into a single step
Now that I have more understanding of bootstrap steps, and a renewed distaste for unnecessary macros, I have managed to express the subtleties of the `tests/coverage` test suite in a single step defined in ordinary code, with no need for helper macros.
Deciding which modes to run is still a bit clunky due to limitations in existing ShouldRun/PathSet APIs, but I think it's a net improvement over having to declare several different steps to handle the suite path and aliases.
The interaction with `--skip` isn't as nice as I'd like, but all of the known limitations are limitations that already existed in the previous implementation.
One minor change is that by default compiletest is now invoked in `coverage-run` mode even when cross-compiling. However, in that situation compiletest still knows that it should skip all of the individual coverage-run tests.
r? jieyouxu (or reassign)
|
|
This accomplishes something like 16a4ad7d7b0d163f7be6803c786c3b83d42913bb,
but with the `rustc_allowed_through_unstable_modules` attribute instead
of the path length.
|
|
fix: Fix a bug that was caused by fixup reversing
|
|
|
|
minor: New clippy lints
|
|
|
|
|
|
These are in symmetry with `{x86_64,i686}-win7-windows-msvc`.
|
|
|
|
|
|
|
|
|
|
fix: Be more permissive with completion resolve data
|
|
|
|
|
|
fix: Fix flycheck getting confused which package to check
|
|
|
|
|
|
Gated behind an unstable `-Z emscripten-wasm-eh` flag
|
|
fix: Handle newstyle `rustc_intrinsic` safety correctly
|
|
|
|
|
|
Signed-off-by: crystalstall <crystalruby@qq.com>
|
|
add m68k-unknown-none-elf target
r? `@workingjubilee`
The existing `m68k-unknown-linux-gnu` target builds `std` by default, requires atomics, and has a base cpu with an fpu. A smaller/more embedded target is desirable both to have a baseline target for the ISA, as well to make debugging easier for working on the llvm backend. Currently this target is using the `M68010` as the minimum CPU due, but as missing features are merged into the `M68k` llvm backend I am hoping to lower this further.
I have been able to build very small crates using a toolchain built against this target (together with a later version of `object`) using the configuration described in the target platform-support documentation, although getting anything of substantial complexity to build quickly hits errors in the llvm backend
|
|
As of the stabilization of `std::backtrace` in Rust 1.65, this package flag has
no effect other than to enable an unused dependency on the `backtrace` crate.
|
|
rustc-dev-guide subtree update
This PR performs the first update of rustc-dev-guide code from its repository.
r? `@BoxyUwU`
|
|
|
|
|
|
|
|
Co-authored-by: Jubilee <workingjubilee@gmail.com>
|
|
(#2192)
|
|
|
|
|
