| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
|
|
|
|
|
|
compiletest: detect non-ICE compiler panics
Fixes #49888, but will be blocked by revealing #49889.
|
|
|
|
|
|
|
|
|
|
Fix the miri tool
r? @eddyb
cc @bjorn3
fixes #49777
|
|
Fix revision support for UI tests.
Fixes #48878
|
|
|
|
|
|
Update Cargo
Some noteble changes:
* ~~regression fix: https://github.com/rust-lang/cargo/pull/5390~~
* ~~potentially breaking bug-fix: https://github.com/rust-lang/cargo/pull/5389~~
* ~~Cargo now caches the result of `rustc -vV`. It checks `rustc` binary
mtime and rustup toolchain settings, so it should probably "just work"
with rustbuild.~~
potentially breaking bug-fix: https://github.com/rust-lang/cargo/pull/5390
|
|
|
|
Some noteble changes:
* regression fix: https://github.com/rust-lang/cargo/pull/5390
* potentially breaking bug-fix: https://github.com/rust-lang/cargo/pull/5389
* Cargo now caches the result of `rustc -vV`. It checks `rustc` binary
mtime and rustup toolchain settings, so it should probably "just work"
with rustbuild.
|
|
Update the Cargo submodule
|
|
|
|
Fixes #48878
|
|
|
|
|
|
Update clippy
r? @Manishearth
|
|
|
|
`foo.nll.stderr`
This allows easy revision of the update-references.sh script (included
here) so that it can update the expected output for nll rather than
stderr. It also reminds the rustc developer via the filename that they
are looking at output generated under comapre-mode=nll.
One could argue that there is still a problem with the strategy encoded here:
if we reach a scenario where a change to the compiler brings the output
under AST and NLL modes back into sync, this code will continue to still
generate output to distinct `foo.stderr` and `foo.nll.stderr` files, and
will continue to copy those two files back to corresponding distinct
files in the source tree, even if the *content* of the two files is now the
same.
* Arguably the "right thing" to do in that case is to remove the
`foo.nll.stderr` file entirely.
* However, I think the real answer is that we will probably want to
double-check such cases by hand anyway. We should be regularly
double-checking the diffs between `foo.stderr` and
`foo.nll.stderr`, and if we see a zero-diff case, then we should
evaluate whether that is correct, and if so, remove the file by
hand.)
* In any case, I think the default behavior encoded here (or at
least *intended* to be encoded here) is superior to the
alternative of *only* generating a `foo.nll.stderr` file if one
already existed in the source tree at the time that `compiletest`
was invoked (and otherwise unconditionally generating a
`foo.stderr` file, as was the behavior prior to this commit),
because that alternative is more likely to cause rustc developers
to overwrite a `foo.stderr` file with the stderr output from a
compare-mode=nll run, which will then break the *normal*
`compiletest` run and probably be much more confusing for the
average rustc developer.
|
|
|
|
E.g. when running with `--compare-mode=nll`, then each test line will
look like e.g.:
```
test [ui (nll)] ui/issue-10969.rs ... ok
```
|
|
|
|
Rollup of 4 pull requests
Successful merges:
- #49699 (Removed 'proc' from the reserved keywords list)
- #49966 (Multiple query search)
- #50013 (Remove no longer necessary comparison to Vec::splice.)
- #50032 (rustdoc: Don't include private paths in all.html)
Failed merges:
|
|
Multiple query search
Part of #49757.
r? @QuietMisdreavus
|
|
prep work for using timely dataflow with NLL
Two major changes:
**Two-phase borrows are overhauled.** We no longer have two bits per borrow. Instead, we track -- for each borrow -- an (optional) "activation point". Then, for each point P where the borrow is in scope, we check where P falls relative to the activation point. If P is between the reservation point and the activation point, then this is the "reservation" phase of the borrow, else the borrow is considered active. This is simpler and means that the dataflow doesn't have to care about 2-phase at all, at last not yet.
**We no longer support using the MIR borrow checker without NLL.** It is going to be increasingly untenable to support lexical mode as we go forward, I think, and also of increasingly little value. This also exposed a few bugs in NLL mode due to increased testing.
r? @pnkfelix
cc @bobtwinkles
|
|
|
|
|
|
|
|
Update Cargo
This includes https://github.com/rust-lang/cargo/pull/5353, which we want to test via opt-in in the wild.
This'll break RLS, the fix is https://github.com/rust-lang-nursery/rls/pull/822
|
|
|
|
|
|
|
|
This includes https://github.com/rust-lang/cargo/pull/5353,
which we might want to test via opt-in in the wild
|
|
Rollup of 14 pull requests
Successful merges:
- #49525 (Use sort_by_cached_key where appropriate)
- #49575 (Stabilize `Option::filter`.)
- #49614 (in which the non-shorthand patterns lint keeps its own counsel in macros)
- #49665 (Small nits to make couple of tests pass on mips targets.)
- #49781 (add regression test for #16223 (NLL): use of collaterally moved value)
- #49795 (Properly look for uninhabitedness of variants in niche-filling check)
- #49809 (Stop emitting color codes on TERM=dumb)
- #49856 (Do not uppercase-lint #[no_mangle] statics)
- #49863 (fixed typo)
- #49857 (Fix "fp" target feature for AArch64)
- #49849 (Add --enable-debug flag to musl CI build script)
- #49734 (proc_macro: Generalize `FromIterator` impl)
- #49730 (Fix ICE with impl Trait)
- #48270 (Replace `structurally_resolved_type` in casts check.)
Failed merges:
|
|
fixed typo
|
|
Update clippy and rls
r? @Manishearth
|
|
Blindly checkpoint status of NLL mode ui tests
This takes the next (and potentially final?) step with #48879.
Namely, this PR got things to the point where I can successfully run `compiletest` on `src/test/ui` with `--compile-mode=nll`.
Here are the main pieces of it:
1. To figure out how to even run `compiletest` normally on the ui directory, I ran `x.py test -vv`, and then looked for the `compiletest` invocation that mentioned `src/test/ui`.
2. I took the aforementioned `compiletest` invocation and used it, adding `--compile-mode=nll` to the end. It had 170 failing cases.
3. Due to #49855, I had to edit some of the tests so that they fail even under NLL, via `#[rustc_error]`. That's the first commit. (Then goto 2 to double-check no such tests remain.)
4. I took the generated `build/target/test/foo.stderr` file for every case that failed, and blindly copied it to `src/test/foo.nll.stderr`. That's the second commit.
5. Goto 2 until there were no failing cases.
6. Remove any stamp files, and re-run `x.py test` to make sure that the edits and new `.nll.stderr` files haven't broken the pre-existing test suite.
|
|
|
|
Move deny(warnings) into rustbuild
This permits easier iteration without having to worry about warnings
being denied.
Fixes #49517
|
|
|
|
|
|
|
|
|
|
This permits easier iteration without having to worry about warnings
being denied.
Fixes #49517
|
|
add THUMB targets to rustup manifest
as instructed in https://github.com/rust-lang/rust/pull/49563#issuecomment-379271327
r? @alexcrichton
|
