| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
This makes it clearer that it is set by the build system rather than by
the rustc that compiles the current rustc. It also avoids bootstrap
needing to pass --check-cfg llvm_enzyme to rustc.
|
|
|
|
|
|
All of the tier 3 targets in the list now link dynamically by default
(except mips64el-unknown-linux-muslabi64, I overlooked that one).
Adjust the list of targets expected to link statically accordingly.
Signed-off-by: Jens Reidel <adrian@travitia.xyz>
|
|
|
|
Only run Cranelift dist test on nightly
Fixes the test failure in https://github.com/rust-lang/rust/pull/146545.
r? `@jieyouxu`
|
|
|
|
|
|
|
|
```
error: unexpected `...`
--> $DIR/varargs-in-closure-isnt-supported.rs:5:20
|
LL | let mut lol = |...| ();
| ^^^ not a valid pattern
|
= note: C-variadic type `...` is not allowed here
```
|
|
|
|
|
|
#[unstable_feature_bound(unsized_const_params)]
|
|
|
|
Remove big-endian swizzles from `vreinterpret`
|
|
see [Zulip
discussion](https://rust-lang.zulipchat.com/#narrow/channel/122651-general/topic/opt-dist.3A.20do.20not.20set.20RUST_LOG.3Dcollector.3Ddebug.20forcefully)
|
|
internal: Add a testing guide
|
|
|
|
|
|
|
|
internal: Add Regression Test For The One And The Only Issue #5514
|
|
|
|
internal: Improve `rust-analyzer diagnostics`
|
|
fix: Don't mark unknown type as implementing every notable trait
|
|
minor: Add regression tests to some S-blocked-on-new-solver issues
|
|
That were fixed by the migration.
|
|
Because the new solver, will return "yes" for them (which is a good thing).
|
|
Rollup of 8 pull requests
Successful merges:
- rust-lang/rust#143314 (add reference id to test, and fix filename)
- rust-lang/rust#146284 (Remove `div_rem` from `core::num::bignum`)
- rust-lang/rust#146416 (Tidy dependency checks cleanups + QoL)
- rust-lang/rust#146471 (bootstrap: Show target in "No such target exists" message)
- rust-lang/rust#146478 (Improve `core::fmt` coverage)
- rust-lang/rust#146480 (tests: update new test to accept new lifetime format)
- rust-lang/rust#146488 (Improve `core::ptr` coverage)
- rust-lang/rust#146501 (compiletest: Fix `--exact` test filtering)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
compiletest: Fix `--exact` test filtering
This fix only changes the behavior when using `--exact` test filtering, which
was quite broken. Before this fix, the following runs 0 tests:
$ ./x test tests/run-make/crate-loading -- --exact
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 431 filtered out; finished in 24.95µs
With the fix the desired test is run:
$ ./x test tests/run-make/crate-loading -- --exact
running 1 tests
test [run-make] tests/run-make/crate-loading ... ok
Without `--exact` the set of run tests is unchanged. This still runs "too many" (cc rust-lang/rust#134341) tests
$ ./x test tests/run-make/crate-loading
running 3 tests
test [run-make] tests/run-make/crate-loading-crate-depends-on-itself ... ok
test [run-make] tests/run-make/crate-loading-multiple-candidates ... ok
test [run-make] tests/run-make/crate-loading ... ok
This still runs the one and only right test
$ ./x test tests/ui/lint/unused/unused-allocation.rs
running 1 tests
test [ui] tests/ui/lint/unused/unused-allocation.rs ... ok
### Notes
- I have not verified this on Windows which treats paths differently (but I see no reason why it should not work since my code should be platform agnostic).
|
|
r=Mark-Simulacrum
Improve `core::ptr` coverage
This PR improves the `core::ptr` coverage by adding a new test to `coretests` for the `<*const T>::is_aligned_to` method.
r? libs
|
|
tests: update new test to accept new lifetime format
Same change as rust-lang/rust@258915a55539593423c3d4c30f7b741f65c56e51, just for a newly written test.
|
|
r=Mark-Simulacrum
Improve `core::fmt` coverage
This PR improves the `core::fmt` coverage by adding new tests to `coretests`
|
|
bootstrap: Show target in "No such target exists" message
This makes it a little easier to pinpoint the issue.
|
|
Tidy dependency checks cleanups + QoL
- Refactors the list of workspaces into a documented struct
- Provide accurate line info in 'Go to ..... for the list' message
- Print crate name on dependency issue (i.e. `dependency for rustc-main` instead of `dependency for .`
|
|
r=Mark-Simulacrum
Remove `div_rem` from `core::num::bignum`
This fixes very old fixme that sounds like this
```
Stupid slow base-2 long division taken from
https://en.wikipedia.org/wiki/Division_algorithm
FIXME use a greater base ($ty) for the long division.
```
By deleting this method since it was never used
|
|
add reference id to test, and fix filename
Noticed the filename is wrong, then took advantage of being there by adding Reference id
|
|
Despite that the `fflags` register (representing floating point
exception flags) is stated as a flag register in the reference, it's not
in the default clobber list of the RISC-V inline assembly and it would
be better to fix it.
|
|
|
|
|
|
|
|
In my experience the `processing <module>` messages make it harder to search for the actual diagnostics, so remove them and instead print the filename only if there is a diagnostic.
Also allow choosing the minimum severity.
|
|
readdir_r has the same problems on FreeBSD as it does on other
platforms: it assumes a fixed NAME_MAX. And readdir has the same
thread-safety guarantee as it does on other platforms: it's safe as long
as only one thread tries to read from the directory stream at a given
time.
Furthermore, readdir_r is likely to be removed for FreeBSD 16, so we
should stop using it now.
|
|
|
|
Since PeekMut implements Deref, it shouldn't have any methods of its
own.
See also: `std::collections::binary_heap::PeekMut::pop`
|
|
Putting this lint in `/methods` is simpler and probably slightly more
efficient.
changelog: [`ptr_offset_with_cast`]: respect MSRV when suggesting fix,
and lint even more cases
|
|
|
|
|
|
|
|
fix: Infinite loop while elaborting predicates
|
