| Age | Commit message (Collapse) | Author | Lines |
|
[beta] backports
- ensure the parent path's existence on `x install` #116349
- Remove `cfg_match` from the prelude #117162
- improve and fix `x install` #117383
- Update to LLVM 17.0.4 #117436
r? cuviper
|
|
(cherry picked from commit 9df857f658ad3acfdf45268952911d51ad58123a)
|
|
Fix: Write access check of `prefix` and `sysconfdir`
when DESTDIR is present.
Improvement: Instead of repeatedly reading `DESTDIR` within
each `fn prepare_dir` usage, read it once and pass it to
the `fn prepare_dir`.
Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit 4b14048d6037a2da5601952a2dd36fe67d04218b)
|
|
(cherry picked from commit 0b96e479ca11daf3bdc5a1a6f002e8bbe516f487)
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
(cherry picked from commit 2c8759ef8a91b70b567a7459694635ed70c19248)
|
|
[beta] backports and stage0 bump
- Bump stage0 to released stable compiler
- Hide host effect params from docs #116670
- Fix a performance regression in obligation deduplication. #116826
- Make `#[repr(Rust)]` and `#[repr(C)]` incompatible with one another #116829
- Update to LLVM 17.0.3 #116840
- Disable effects in libcore again #116856
- revert rust-lang/rust#114586 #116879
r? cuviper
|
|
[beta-1.74] Update cargo
1 commits in 22a976c6fb1bef45abcf182b4c7def87ad8b4a4d..ecb9851afd3095e988daaa35a48bc7f3cb748e04
2023-10-12 00:06:40 +0000 to 2023-10-18 20:42:16 +0000
- [beta-1.74.0] Partial-version spec support (rust-lang/cargo#12847)
r? ghost
|
|
(cherry picked from commit a1e274f1721f6be4a36afe10e57a6825eeeaf848)
|
|
(cherry picked from commit bcdd3d77397295f1e20cd257c306d25c3a32dde2)
|
|
(cherry picked from commit ab22470eb3592f41634e411ffe98343f70053e57)
|
|
(cherry picked from commit d0b99e3efe62b5acc107da9c84331eae6cbe5a0d)
|
|
Commit 8378487 from #114611 changed the location of an obligation
deduplication step in `opt_normalize_projection_type`. This meant that
deduplication stopped happening on one path where it was still
necessary, causing a couple of drastic performance regressions.
This commit moves the deduplication back to the old location. The good
news is that #114611 had four commits and 8378487 was of minimal
importance, so the perf benefits from that PR remain.
Fixes #116780, #116797.
(cherry picked from commit 91f2fbc867bfc31f2e103b09e605c61f1a450b33)
|
|
const trait things in libcore
(cherry picked from commit 16f8396f6df6902eeef580396785ab8888c3718b)
|
|
(cherry picked from commit 6724f9926c9e8c2d37e3e68e44238897bd89fddf)
|
|
(cherry picked from commit cfb6afa2965a1504f366eb258193219c4a820141)
|
|
(cherry picked from commit 8f2af7e010945e6d57e839db2673e276e8bf6532)
|
|
(cherry picked from commit c4e61faf2e078dc30b62488326404137600e5e11)
|
|
(cherry picked from commit 20363f40a938d05df68a775bacc9ca52c7490c7c)
|
|
|
|
|
|
[beta-1.74] Update cargo
1 commits in 59596f0f31a94fde48b5aa7e945cd0b7ceca9620..22a976c6fb1bef45abcf182b4c7def87ad8b4a4d
2023-09-29 19:29:17 +0000 to 2023-10-12 00:06:40 +0000
- [beta 1.74] Update curl-sys to pull in curl 8.4.0 (rust-lang/cargo#12809)
r? `@ehuss`
|
|
|
|
[beta] promote release
r? `@Mark-Simulacrum`
|
|
This should fix running tests on the emscripten target. In the future
it's expected we'll want to entirely remove this builder since it's a
tier 2 target, but for this initially beta-targeted patch keeping the
changes minimal is preferred.
|
|
|
|
|
|
Pass `-jN` from Make to `BOOTSTRAP_ARGS`
Enables the same functionality as `x -jN` in Make by passing the `-jN` arg from Make to the `BOOTSTRAP_ARGS` if it is specified.
|
|
quote argument to sh -n
This prevents glob expansion (*.py) and field splitting
|
|
Document that Instant may or may not include system-suspend time
Since people are still occasionally surprised by this let's make it more explicit. This doesn't add any new guarantees, only documents the status quo.
Related issues: #87906 #79462
|
|
add sanity checks for user write access on `x install`
Resolves #113580
|
|
Add Oğuz Ağcayazı to .mailmap
this will merge my commits under one name (hopefully)
|
|
Assorted improvements for `rustc_middle::mir::traversal`
r? `@cjgillot`
I'm not _entirely_ sure about all changes, although I do like all of them. If you'd like I can drop some commits. Best reviewed on a commit-by-commit basis, I think, since they are fairly isolated.
|
|
|
|
r=GuillaumeGomez
rustdoc: speed up processing of cross-crate fns to fix a perf regression
* The first commit doesn't affect perf but get's rid of a `.clone()` and a bunch of lines of code. I can drop it if you'd like me to
* The second commit, *“reduce the amount of `asyncness` query executions”*, addresses the perf regression introduced in #116084
r? `@ghost`
|
|
Update cargo
4 commits in e6aabe8b3fcf639be3a5bf68e77853bd7b3fa27d..59596f0f31a94fde48b5aa7e945cd0b7ceca9620
2023-09-26 16:31:53 +0000 to 2023-09-29 19:29:17 +0000
- refactor: Switch from termcolor to anstream (rust-lang/cargo#12751)
- Add missing `strip` entries in `dev` and `release` profiles. (rust-lang/cargo#12748)
- Add better suggestion for the unsupported silent flag (rust-lang/cargo#12723)
- docs(ref): Establish publish best practices (rust-lang/cargo#12745)
r? ghost
|
|
Prototype using const generic for simd_shuffle IDX array
cc https://github.com/rust-lang/rust/issues/85229
r? `@workingjubilee` on the design
TLDR: there is now a `fn simd_shuffle_generic<T, U, const IDX: &'static [u32]>(x: T, y: T) -> U;` intrinsic that allows replacing
```rust
simd_shuffle(a, b, const { stuff })
```
with
```rust
simd_shuffle_generic::<_, _, {&stuff}>(a, b)
```
which makes the compiler implementations much simpler, if we manage to at some point eliminate `simd_shuffle`.
There are some issues with this today though (can't do math without bubbling it up in the generic arguments). With this change, we can start porting the simple cases and get better data on the others.
|
|
Weaken needlessly restrictive orderings on Arc::*_count
Follow up to https://github.com/rust-lang/rust/pull/95183 from this zulip: https://rust-lang.zulipchat.com/#narrow/stream/219381-t-libs/topic/Why.20does.20Arc.3A.3Astrong_count.20use.20Acquire.20instead.20of.20Relaxed.3F/near/386213850
I'd like to use the strong_count for a lockless algorithm I'm writing, but I don't need acquire semantics so that's pointlessly restrictive on arm/risc-v.
|
|
|
|
Promote loongarch64-unknown-none* to Tier 2
MCP: https://github.com/rust-lang/compiler-team/issues/664
|
|
|
|
|
|
Rollup of 6 pull requests
Successful merges:
- #112123 (fix(suggestion): insert projection to associated types)
- #116024 (Implement Region for smir)
- #116030 (run abi/compatibility test against a whole bunch of targets)
- #116216 (ci: upgrade to crosstool-ng 1.26.0)
- #116241 (Add Exclusive forwarding impls (FnOnce, FnMut, Generator))
- #116263 (More fixes for running the test suite on a bare metal target)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
More fixes for running the test suite on a bare metal target
This PR adds more fixes needed to run the test suite on bare metal targets (in this case, without unwinding and with static relocations). There is no CI job exercising tests without unwinds, but I can confirm this worked in Ferrocene's CI.
|
|
Add Exclusive forwarding impls (FnOnce, FnMut, Generator)
This is adapted from #104057.
|
|
ci: upgrade to crosstool-ng 1.26.0
This PR upgrades our builders from crosstool-ng 1.25.0 to 1.26.0. Except for LoongArch64 and RISC-V 64, which have minor version upgrades, other architectures have not changed.
|
|
run abi/compatibility test against a whole bunch of targets
|
|
Implement Region for smir
Adds Region and it's relevant types to smir and covers them with stable implementation
r? `@oli-obk`
|
|
fix(suggestion): insert projection to associated types
Fixes #98562
This PR has fixed some help suggestions for unsupported syntax, such as `fn f<T>(_:T) where T: IntoIterator, std::iter::IntoIterator::Item = () {}` to `fn f<T: IntoIterator<Item = ()>>(_T) {}`.
|
|
|
|
stabilize combining +bundle and +whole-archive link modifiers
Per discussion on https://github.com/rust-lang/rust/issues/108081 combining +bundle and +whole-archive already works and can be stabilized independently of other aspects of the packed_bundled_libs feature. There is no risk of regression because this was not previously allowed.
r? `@petrochenkov`
|