| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
vec tets: ensure pointer is still writeable
Under Tree Borrows, a pointer can become read-only: still allowing reads but not permitting writes any more. So these tests that want to check that pointers remain valid need to do writes to ensure that pointers indeed remain fully valid.
|
|
|
|
Automatic sync from rustc
|
|
|
|
|
|
|
|
|
|
This should avoid CI breakage when the LLVM stamp is updated, and also it will avoid an unnecessary LLVM download from CI.
|
|
|
|
Rollup of 3 pull requests
Successful merges:
- #113253 (Fixed documentation of from<CString> for Rc<CStr>: Arc -> Rc)
- #113258 (Migrate GUI colors test to original CSS color format)
- #113259 (Suggest `x build library` for a custom toolchain that fails to load `core`)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Rewrite `UnDerefer`
Currently, `UnDerefer` is used by drop elaboration to undo the effects of the `Derefer` pass. However, it just recreates the original places with derefs in the middle of the projection. Because `ProjectionElem::Deref` is intended to be removed completely in the future, this will not work forever.
This PR introduces a `deref_chain` method that returns the places behind `DerefTemp` locals in a place and rewrites the move path code to use this. In the process, `UnDerefer` was merged into `MovePathLookup`. Now that move paths use the same places as in the MIR, the other uses of `UnDerefer` no longer require it.
See #98145
cc `@ouz-a`
r? `@oli-obk`
|
|
Backtrace 0.3.68
Uptakes these releases:
- https://github.com/rust-lang/backtrace-rs/releases/tag/0.3.68
r? `@thomcc`
|
|
Dedup addr2line, miniz_oxide, object in .lock
|
|
Suggest `x build library` for a custom toolchain that fails to load `core`
Fixes #113222
r? `@jyn514`
|
|
Migrate GUI colors test to original CSS color format
Follow-up of https://github.com/rust-lang/rust/pull/111459.
r? `@notriddle`
|
|
Fixed documentation of from<CString> for Rc<CStr>: Arc -> Rc
Fix #113131
|
|
cargo update
#112865 with the tidy exemptions and tracing and syn 2 not upgraded
Additional deps:
equivalent: indexmap
errno: through rustix
errno-dragonfly: errno
nu-ansi-term: tracing
overload: nu-ansi-term
r? Mark-Simulacrum
|
|
cron auto-PR: can't seem to avoid repeating the branch name...
|
|
|
|
|
|
sadly 'gh' doesnt support all git upstream branch configs
|
|
|
|
The outline-atomics support in compiler_builtins messed up and wasn't limited to linux only.
https://github.com/rust-lang/compiler-builtins/pull/532/files#r1249354225
|
|
See https://github.com/rust-lang/rust/pull/113046#issuecomment-1616094626.
|
|
There's currently a deadlock with tracing when RUSTC_LOG is enabled.
Downgrade tracing-core for now to avoid blocking the other updates.
syns upgrades cause some nontrivial changes in the diagnostics derive tests,
which are best dealt with in another PR.
|
|
GuillaumeGomez:rustdoc-search-whitespace-as-separator, r=notriddle
rustdoc: Allow whitespace as path separator like double colon
Fixes https://github.com/rust-lang/rust/issues/108447.
I think it makes sense since it allows more common cases, however it also makes the syntax heavier. Not sure what the rest of the team thinks about it. In any case we'll need to go through FCP.
Full explanation for the changes is available [here](https://github.com/rust-lang/rust/pull/108537#issuecomment-1589480564).
r? `@notriddle`
|
|
Additional deps:
equivalent: indexmap
nu-ansi-term: tracing
overload: nu-ansi-term
|
|
cronjob auto-PR: try to fix setting the remote branch
|
|
|
|
cargo-miri: better error message when RUSTC is not set
Currently, when running `cargo-miri` instead of `cargo miri` you get a very confusing.
```
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: NotPresent', src/tools/miri/cargo-miri/src/main.rs:83:41
```
error. This replaces that with a message telling them to use `cargo miri`
|
|
cron auto-PR: need to set upstream branch
|
|
|
|
Update Clippy
r? `@Manishearth`
cc `@oli-obk` (for the ui-test changes in de69d556eb5006a21f868b8c12d48f0ef1308a5a and the valtree fix in 0cbe963e51faa7e3e771c1f9cea9aa443a648455)
Fixes https://github.com/rust-lang/rust/issues/102093
This must've been the most involved Clippy sync ever.
|
|
|
|
|
|
|
|
|
|
|
|
Add `-Zremark-dir` unstable flag to write LLVM optimization remarks to YAML
This PR adds an option for `rustc` to emit LLVM optimization remarks to a set of YAML files, which can then be digested by existing tools, like https://github.com/OfekShilon/optview2. When `-Cremark-dir` is passed, and remarks are enabled (`-Cremark=all`), the remarks will be now written to the specified directory, **instead** of being printed to standard error output. The files are named based on the CGU from which they are being generated.
Currently, the remarks are written using the LLVM streaming machinery, directly in the diagnostics handler. It seemed easier than going back to Rust and then form there back to C++ to use the streamer from the diagnostics handler. But there are many ways to implement this, of course, so I'm open to suggestions :)
I included some comments with questions into the code. Also, I'm not sure how to test this.
r? `@tmiasko`
|
|
cronjob auto-PR: fetch more of the history
|
|
|
|
|
|
|
|
Rollup of 8 pull requests
Successful merges:
- #113147 (Fix document examples of Vec::from_raw_parts and Vec::from_raw_parts_in)
- #113202 (std docs: factorize literal in Barrier example)
- #113228 (Migrate GUI colors test to original CSS color format)
- #113231 (Fix `dropping_copy_types` lint from linting in match-arm with side-effects)
- #113233 (Update chalk)
- #113234 (Don't pass --test-args to `python -m unitest`)
- #113244 (Make Rust Analyzer tests faster by compiling less code)
- #113249 (Document tracking issue for rustdoc `show-type-layout`)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
cronjob auto-PR: make sure we are on a branch
Also run this every hour to speed up testing
|
|
|
|
|