| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Rustc pull update
|
|
|
|
|
|
Faster fmt::Display of 128-bit integers, without unsafe pointer
In followup of #135265, hereby the 128-bit part.
* Batches per 16 instead of 19 digits
* Buffer access as array insteaf of unsafe pointer
* Added test coverage for i128 and u128
r? tgross35 ChrisDenton
|
|
Rollup of 9 pull requests
Successful merges:
- rust-lang/rust#142305 (Remove unneeded `check_id` calls as they are already called in `visit_id` in `EarlyContextAndPass` type)
- rust-lang/rust#142314 (remove ice group pings from `triagebot.toml`)
- rust-lang/rust#142343 (remove myself from the project)
- rust-lang/rust#142346 (Add tracing import to execution context)
- rust-lang/rust#142356 (Fix enter_trace_span!() using wrong $crate paths)
- rust-lang/rust#142362 (Add expectation for `{` when parsing lone coroutine qualifiers)
- rust-lang/rust#142364 (Do not warn on `rust.incremental` when using download CI rustc)
- rust-lang/rust#142369 (Improve some attribute docs and rename groups)
- rust-lang/rust#142374 (Fix missing newline trim in bootstrap)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
Fix missing newline trim in bootstrap
Fixes [this comment](https://github.com/rust-lang/rust/pull/141909/files#r2140632918).
Fixes: https://github.com/rust-lang/rust/issues/142350
|
|
Improve some attribute docs and rename groups
r? `@nnethercote`
Some naming here got changed at some point, and this feels more consistent. The docs changes were a direct response to `@mejrs` trying to implement a new parsers and running into this.
|
|
r=RalfJung
Do not warn on `rust.incremental` when using download CI rustc
Discussed on Zulip.
r? `@RalfJung`
|
|
Add expectation for `{` when parsing lone coroutine qualifiers
Fixes https://github.com/rust-lang/rust/issues/80931
|
|
Fix enter_trace_span!() using wrong $crate paths
This is a followup to rust-lang/rust#140972, where I made a silly mistake and forgot to update `$crate::interpret::tracing_utils::...` to `$crate::interpret::util::...` inside the macro after moving the referenced code from `tracing_utils.rs` to `util.rs`. Sorry about this.
r? `@RalfJung`
|
|
Shourya742:2025-06-11-add-tracing-import-to-execution-context, r=Kobzol
Add tracing import to execution context
In https://github.com/rust-lang/rust/pull/141909, we missed adding the trace_cmd import in the execution context module. This PR fixes that. Additionally, we are updating the mingw-check-2 check command to include BOOTSTRAP_TRACING=1 to help ensure we don't miss such cases in future PRs.
r? `@Kobzol`
|
|
remove myself from the project
See [#t-infra/bootstrap > stepping down from T-Bootstrap](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/stepping.20down.20from.20T-Bootstrap/with/523501689)
|
|
remove ice group pings from `triagebot.toml`
Followup to rust-lang/team#1860.
Question: should the https://github.com/rust-lang/rust/labels/ICEBreaker-Cleanup-Crew and https://github.com/rust-lang/rust/labels/ICEBreaker-LLVM labels be deleted too or not?
|
|
GuillaumeGomez:remove-visit_id-EarlyContextAndPass, r=oli-obk
Remove unneeded `check_id` calls as they are already called in `visit_id` in `EarlyContextAndPass` type
Follow-up from [this message](https://github.com/rust-lang/rust/pull/142240/files#r2137474724).
Since `check_id` is already called in `visit_id` which is supposed to be called for each item with an ID, we don't need to manually call `check_id`.
r? `@oli-obk`
|
|
Rollup of 9 pull requests
Successful merges:
- rust-lang/rust#141967 (Configure bootstrap backport nominations through triagebot)
- rust-lang/rust#142042 (Make E0621 missing lifetime suggestion verbose)
- rust-lang/rust#142272 (tests: Change ABIs in tests to more future-resilient ones)
- rust-lang/rust#142282 (Only run `citool` tests on the `auto` branch)
- rust-lang/rust#142297 (Implement `//@ needs-target-std` compiletest directive)
- rust-lang/rust#142298 (Make loongarch-none target maintainers more easily pingable)
- rust-lang/rust#142306 (Dont unwrap and re-wrap typing envs)
- rust-lang/rust#142324 (Remove unneeded `FunctionCx` from some codegen methods)
- rust-lang/rust#142328 (feat: Add `bit_width` for unsigned integer types)
Failed merges:
- rust-lang/rust#141639 (Expose discriminant values in stable_mir)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
|
|
|
|
|
|
|
|
Revert "add `Cargo.lock` to CI-rustc allowed list for non-CI env"
This reverts commit c3de813944873940b8e1a7734991f3c9f3f55156 (https://github.com/rust-lang/rust/pull/142232).
r? `@RalfJung`
Fixes: https://github.com/rust-lang/rust/issues/142338
Unfixes: https://github.com/rust-lang/rust/issues/141986
|
|
|
|
|
|
feat: Add `bit_width` for unsigned integer types
- Accepted ACP: rust-lang/libs-team#598
- Tracking issue: rust-lang/rust#142326
This PR adds methods to the primitive unsigned integer types that return the minimum number of bits required to represent an unsigned integer.
|
|
Remove unneeded `FunctionCx` from some codegen methods
No changes; just removing the `self` that wasn't needed.
r? workingjubilee
cc https://github.com/rust-lang/rust/pull/138759#issuecomment-2920860686
|
|
Dont unwrap and re-wrap typing envs
Just a tiny tweak to make the query less awkward.
r? lcnr
|
|
Make loongarch-none target maintainers more easily pingable
In the same style as rust-lang/rust#139028.
r? compiler
|
|
Implement `//@ needs-target-std` compiletest directive
Closes rust-lang/rust#141863.
Needed to unblock rust-lang/rust#139244 and rust-lang/rust#141856.
### Summary
This PR implements a `//@ needs-target-std` compiletest directive that gates test execution based on whether the target supports std or not. For some cases, this should be preferred over e.g. some combination of `//@ ignore-none`, `//@ ignore-nvptx` and more[^none-limit].
### Implementation limitation
Unfortunately, since there is currently [no reliable way to determine from metadata whether a given target supports std or not](https://github.com/rust-lang/rust/issues/142296), we have to resort to a hack. Bootstrap currently determines whether or not a target supports std by a naive target tuple substring comparison: a target supports std if its target tuple does *not* contain one of `["-none", "nvptx", "switch"]` substrings. This PR simply pulls that hack out into `build_helpers` to avoid reimplementing the same hack in compiletest, and uses that logic to inform `//@ needs-target-std`.
### Auxiliary changes
This PR additionally changes a few run-make tests to use `//@ needs-target-std` over an inconsistent combination of target-based `ignore`s. This should help with rust-lang/rust#139244.
---
r? bootstrap
[^none-limit]: Notably, `target_os = "none"` is **not** a sufficient condition for "target does not support std"
|
|
Only run `citool` tests on the `auto` branch
Proposed here: [#t-infra > PR ci seems much to slow @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/PR.20ci.20seems.20much.20to.20slow/near/523159583). I haven't yet seen these tests failing on CI, so I think it's a good trade-off.
r? `````@marcoieni`````
|
|
tests: Change ABIs in tests to more future-resilient ones
Eventually we're going to make these tests not work as they are currently written on HEAD, so change them now to get ahead of that.
r? aDotInTheVoid
|
|
r=compiler-errors
Make E0621 missing lifetime suggestion verbose
```
error[E0621]: explicit lifetime required in the type of `x`
--> $DIR/42701_one_named_and_one_anonymous.rs:10:9
|
LL | &*x
| ^^^ lifetime `'a` required
|
help: add explicit lifetime `'a` to the type of `x`
|
LL | fn foo2<'a>(a: &'a Foo, x: &'a i32) -> &'a i32 {
| ++
```
Part of rust-lang/rust#141973.
|
|
Configure bootstrap backport nominations through triagebot
Following the discussion in [#t-infra/bootstrap > ✔ Have triagebot create backport nomination threads?](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/.E2.9C.94.20Have.20triagebot.20create.20backport.20nomination.20threads.3F/with/521876500) where we noticed that bootstrap backport nominations were difficult to track, since:
- We don't really have a dedicated person / group of people checking for bootstrap backport nominations.
- We don't really have an establish way of handling bootstrap backports.
This PR configures triagebot to open backport nominations threads (indicated for bootstrap team if a given PR has the suitable team label, https://github.com/rust-lang/rust/labels/T-bootstrap) in [#t-infra/bootstrap/backports](https://rust-lang.zulipchat.com/#narrow/channel/507486-t-infra.2Fbootstrap.2Fbackports). The current configuration is such that **the whole bootstrap team will be pinged for bootstrap backport nominations**[^diverges].
### Steps
- [x] ~~Ping members who opt-in subscribe to backport channel, or ping the whole bootstrap team?~~
- Poll: [#t-infra/bootstrap > Have triagebot create backport nomination threads? @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/Have.20triagebot.20create.20backport.20nomination.20threads.3F/near/522141337)
- Votes (as of 2025-06-10): 3 votes "no preference", 1 vote "in favor".
- [x] ~~(Best for follow-up) Maybe also document bootstrap team's backport process / decision process in Forge? It's a bit different from [compiler team's backport process](https://forge.rust-lang.org/compiler/backports.html) because we don't have weekly bootstrap triage meetings and thus don't have sync backport decisions.~~
- Tracked as follow-up in Forge: https://github.com/rust-lang/rust-forge/issues/889.
---
r? Kobzol
[^diverges]: Note that this configuration is similar to the types team backport nominations, but diverges from the compiler team.
|
|
`FIXME(-Znext-solver)` triage
r? `@BoxyUwU`
|
|
|
|
|
|
|
|
|
|
This reverts commit c3de813944873940b8e1a7734991f3c9f3f55156.
|
|
Signed-off-by: onur-ozkan <work@onurozkan.dev>
|
|
|
|
Implement representation options to smir
Resolves rust-lang/project-stable-mir#89
|
|
that was phrased like a separate sentence
|
|
|
|
Make root vars more stable
Never resolve a ty/ct vid to a higher vid as its root. This should make the optimization in rust-lang/rust#141500 more "stable" when there are a lot of vars flying around.
r? `@ghost`
|
|
|
|
Remove check_mod_loops query and run the checks per-body instead
This analysis is older than my first rustc contribution I believe. It was never querified. Ideally we'd merge it into the analysis happening within typeck anyway (typeck just uses span_delayed_bug instead of erroring), but I didn't want to do that within this PR that also moves things around and subtly changes diagnostic ordering.
|
|
No changes; just removing the `self` that wasn't needed.
|
|
|
|
Miri subtree update
r? `@ghost`
|
|
|
|
`EarlyContextAndPass` type
|
