owner stringclasses 16
values | repo stringclasses 17
values | id int64 116k 4.2B | issue_number int32 1 155k | author stringlengths 0 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-04-08 05:18:21 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-04-08 05:18:21 | reactions unknown | author_association stringclasses 7
values |
|---|---|---|---|---|---|---|---|---|---|
rust-lang | rust | 3,024,935,936 | 137,018 | ChrisDenton | Basically there's no reason to use `cdecl` or `stdcall` on Windows. | 2025-07-01T17:30:50 | 2025-07-01T17:30:50 | {} | MEMBER |
rust-lang | rust | 3,024,577,038 | 143,048 | Kobzol | r? @jieyouxu | 2025-07-01T15:44:13 | 2025-07-01T15:44:13 | {} | MEMBER |
rust-lang | rust | 3,024,618,655 | 143,208 | rust-timer | Finished benchmarking commit (e3a4b05fb719511c7b8d0306c3a9e0445abcdfda): [comparison URL](https://perf.rust-lang.org/compare.html?start=f46ce66fcc3d6058f90ac5bf0930f940f1e7b0ca&end=e3a4b05fb719511c7b8d0306c3a9e0445abcdfda&stat=instructions:u).
### Overall result: ✅ improvements - no action needed
Benchmarking this p... | 2025-07-01T15:56:56 | 2025-07-01T15:56:56 | {
"hooray": 3
} | COLLABORATOR |
rust-lang | rust | 3,024,898,209 | 143,194 | workingjubilee | Oh, sorry!
@bors r+ rollup | 2025-07-01T17:16:25 | 2025-07-01T17:16:25 | {} | MEMBER |
rust-lang | rust | 3,024,905,928 | 143,285 | rust-bors[bot] | :broken_heart: Test failed
- [CI](https://github.com/rust-lang/rust/actions/runs/16003442005) :x: | 2025-07-01T17:19:24 | 2025-07-01T17:19:24 | {} | CONTRIBUTOR |
rust-lang | rust | 3,024,988,452 | 141,219 | RalfJung | I had pushed a Miri fix into this PR in the past... did that get force-pushed away? | 2025-07-01T17:48:59 | 2025-07-01T17:48:59 | {} | MEMBER |
rust-lang | rust | 3,025,023,864 | 141,509 | Amanieu | We discussed this in the @rust-lang/libs-api meeting. We felt that the main argument against making these associated function is that unlike `Box`/`Arc`/`Rc`, `Vec` doesn't `Deref` to an arbitrary `T` but instead to a slice type which has a fixed set of methods which we know this will not conflict with.
@rfcbot clos... | 2025-07-01T18:01:42 | 2025-07-01T18:01:42 | {} | MEMBER |
rust-lang | rust | 3,024,543,504 | 143,286 | rustbot | r? @WaffleLapkin
rustbot has assigned @WaffleLapkin.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.
Use `r?` to explicitly pick a reviewer | 2025-07-01T15:34:19 | 2025-07-01T15:34:19 | {} | COLLABORATOR |
rust-lang | rust | 3,008,739,068 | 143,048 | rust-log-analyzer |
The job **`mingw-check-1`** failed! Check out the build log: [(web)](https://github.com/rust-lang/rust/actions/runs/15904675257/job/44856304524) [(plain)](https://github.com/rust-lang/rust/commit/a36ee2459c68b6f455b1f65af313534407957954/checks/44856304524/logs)
<details><summary><i>Click to see the possible cause of ... | 2025-06-26T14:40:44 | 2025-07-01T15:43:54 | {} | COLLABORATOR |
rust-lang | rust | 3,024,708,451 | 140,871 | Amanieu | I've updated the PR to only allow labels in non-generic naked functions. | 2025-07-01T16:18:08 | 2025-07-01T16:18:08 | {} | MEMBER |
rust-lang | rust | 3,024,758,823 | 142,321 | workingjubilee | ??? misclick.
@bors r+ | 2025-07-01T16:35:21 | 2025-07-01T16:35:21 | {
"hooray": 1
} | MEMBER |
rust-lang | rust | 3,014,649,894 | 134,628 | bors | :umbrella: The latest upstream changes (presumably #143064) made this pull request unmergeable. Please [resolve the merge conflicts](https://rustc-dev-guide.rust-lang.org/git.html#rebasing-and-conflicts). | 2025-06-27T23:34:31 | 2025-07-01T17:20:45 | {} | COLLABORATOR |
rust-lang | rust | 3,024,993,221 | 141,219 | RalfJung | Yeah, looks like it...
@Amanieu I would recommend never using `push -f`, and always using `push --force-with-lease`; that greatly reduces the risk of issues like this. This alias in .gitconfig helps:
```
[alias]
pushf = push --force-with-lease
``` | 2025-07-01T17:50:43 | 2025-07-01T17:50:43 | {} | MEMBER |
rust-lang | rust | 3,025,005,564 | 137,018 | RalfJung | > Does system coincide with stdcall on ARM64 and x64 machines?
There's no such thing as stdcall on ARM64, is there...?
Or do you mean, "the thing that MSVC does when you use stdcall on ARM64"? AFAIK, it just ignores the stdcall, silently, and uses the normal C ABI instead. So in that sense "system" is the same thing, ... | 2025-07-01T17:55:15 | 2025-07-01T17:55:15 | {} | MEMBER |
rust-lang | rust | 3,025,009,690 | 141,219 | bors | :pushpin: Commit 8797d54812393baeff99ffe257fa056c3dfdb656 has been approved by `joboet`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=joboet 8797d54812393baeff99ffe257fa056c3dfdb656 -->
<!-- homu: {"type":"Approved","sha":"8797d54812393baeff99ffe257fa056c3dfdb6... | 2025-07-01T17:56:57 | 2025-07-01T17:56:57 | {} | COLLABORATOR |
rust-lang | rust | 3,025,012,767 | 142,974 | cuviper | Rebased, and removed another new miri `bootstrap`.
@bors r=Mark-Simulacrum | 2025-07-01T17:58:03 | 2025-07-01T17:58:03 | {} | MEMBER |
rust-lang | rust | 3,025,026,714 | 141,509 | Amanieu | @rfcbot close | 2025-07-01T18:02:36 | 2025-07-01T18:02:36 | {} | MEMBER |
rust-lang | rust | 3,025,037,175 | 137,018 | pronebird | > > Does system coincide with stdcall on ARM64 and x64 machines?
>
> There's no such thing as stdcall on ARM64, is there...? Or do you mean, "the thing that MSVC does when you use stdcall on ARM64"? AFAIK, it just ignores the stdcall, silently, and uses the normal C ABI instead. So in that sense "system" is the same t... | 2025-07-01T18:06:33 | 2025-07-01T18:11:44 | {} | NONE |
rust-lang | rust | 3,025,050,937 | 113,382 | bors | :umbrella: The latest upstream changes (presumably #142030) made this pull request unmergeable. Please [resolve the merge conflicts](https://rustc-dev-guide.rust-lang.org/git.html#rebasing-and-conflicts). | 2025-07-01T18:12:20 | 2025-07-01T18:12:20 | {} | COLLABORATOR |
rust-lang | rust | 3,024,795,768 | 143,247 | rust-timer | Queued 3797379f7091833992e5116135662ecd38c057d2 with parent 86e05cd300fac9e83e812c4d46582b48db780d8f, future [comparison URL](https://perf.rust-lang.org/compare.html?start=86e05cd300fac9e83e812c4d46582b48db780d8f&end=3797379f7091833992e5116135662ecd38c057d2).
There is currently 1 preceding artifact in the [queue](https... | 2025-07-01T16:48:12 | 2025-07-01T18:12:45 | {} | COLLABORATOR |
rust-lang | rust | 3,024,920,564 | 143,191 | rfcbot | @Amanieu proposal cancelled. | 2025-07-01T17:24:51 | 2025-07-01T18:20:05 | {} | NONE |
rust-lang | rust | 3,024,636,627 | 142,097 | oli-obk | > I don't want to add any actual run tests, as these would require a working clang based on the same commit.
why is clang necessary for this? | 2025-07-01T16:02:04 | 2025-07-01T16:02:04 | {} | CONTRIBUTOR |
rust-lang | rust | 3,024,673,146 | 142,849 | Amanieu | Could you expand on the motivation for this change. Specifically, could you give a code example where this is used and you recover the number of bytes actually written to the buffer. We discussed this in the @rust-lang/libs-api meeting and it seems like this use case may perhaps be better serve with some sort of cursor... | 2025-07-01T16:12:04 | 2025-07-01T16:12:04 | {} | MEMBER |
rust-lang | rust | 3,024,825,594 | 143,009 | GuillaumeGomez | Gonna take a look. | 2025-07-01T16:55:38 | 2025-07-01T16:55:38 | {
"heart": 1
} | MEMBER |
rust-lang | rust | 3,024,833,312 | 123,617 | rcvalle | I've resolved the merge conflicts on this PR and removed the commit that would stabilize the no_sanitize attribute in favor of #142681. @traviscross @wesleywiser whenever you have time, let me know if these PRs look good to you and/or if there are any pending concerns. | 2025-07-01T16:57:40 | 2025-07-01T16:57:40 | {} | MEMBER |
rust-lang | rust | 3,024,888,141 | 143,288 | Kobzol | @bors r+ rollup | 2025-07-01T17:13:04 | 2025-07-01T17:13:04 | {} | MEMBER |
rust-lang | rust | 3,024,913,130 | 141,385 | estebank | @chenyukang yeah, uplifting this to `rustc_list` would make sense, IMO. | 2025-07-01T17:22:28 | 2025-07-01T17:22:28 | {} | CONTRIBUTOR |
rust-lang | rust | 3,024,917,546 | 137,018 | pronebird | Windows API functions are marked with `stdcall`. Does `system` coincide with `stdcall` on ARM64 and x64 machines? | 2025-07-01T17:23:37 | 2025-07-01T17:23:37 | {} | NONE |
rust-lang | rust | 3,025,019,417 | 143,266 | folkertdev | I made some progress here actually. I believe that I should add this bit of logic to `compiler/rustc_codegen_ssa/src/mono_item.rs`:
```rust
if cx
.tcx()
.codegen_fn_attrs(instance.def_id())
.flags
.contains(CodegenFnAttrFla... | 2025-07-01T18:00:02 | 2025-07-01T18:00:02 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,082,066 | 143,137 | rust-bors[bot] | :hourglass: Trying commit 47b18718a6676c018c8bf0aa6ded18dce7073b01 with merge 5c2b93b344363e75a6149aeb2cfe11a087129533…
To cancel the try build, run the command `@bors2 try cancel`.
| 2025-06-28T21:56:01 | 2025-06-28T21:56:01 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,094,102 | 142,021 | bors | :pushpin: Commit 2760b246fb051bc066406c6ffa692bdeb51a7cbf has been approved by `ehuss`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=ehuss 2760b246fb051bc066406c6ffa692bdeb51a7cbf -->
<!-- homu: {"type":"Approved","sha":"2760b246fb051bc066406c6ffa692bdeb51a7cbf... | 2025-06-28T22:16:52 | 2025-06-28T22:16:52 | {} | COLLABORATOR |
rust-lang | rust | 3,016,034,541 | 142,974 | rust-log-analyzer |
The job **`dist-i586-gnu-i586-i686-musl`** failed! Check out the build log: [(web)](https://github.com/rust-lang/rust/actions/runs/15947660506/job/44983721340) [(plain)](https://github.com/rust-lang/rust/commit/233101ce65341db6e721dda98c11faeb4a890204/checks/44983721340/logs)
<details><summary><i>Click to see the pos... | 2025-06-28T21:15:25 | 2025-06-28T23:02:35 | {
"hooray": 1
} | COLLABORATOR |
rust-lang | rust | 3,016,202,050 | 143,160 | bors | :hourglass: Testing commit e0c8c3fbb049b278c286d7efd9ca90fe14763f32 with merge 8141c2265f5f2b26d89abe8df5fa67286f2425d4...
<!-- homu: {"type":"BuildStarted","head_sha":"e0c8c3fbb049b278c286d7efd9ca90fe14763f32","merge_sha":"8141c2265f5f2b26d89abe8df5fa67286f2425d4"} --> | 2025-06-29T01:16:21 | 2025-06-29T01:16:21 | {} | COLLABORATOR |
rust-lang | rust | 3,016,218,956 | 143,138 | jdonszelmann | @bors r+ | 2025-06-29T01:59:15 | 2025-06-29T01:59:15 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,033,311 | 134,000 | workingjubilee | This does indeed seem to have been the case! We have a few mentions of these debug intrinsics in our codebase but we don't *actually* call them directly, unlike other intrinsics. We call the builder "properly". | 2025-06-28T21:11:37 | 2025-06-28T21:11:37 | {} | MEMBER |
rust-lang | rust | 3,016,057,794 | 143,160 | ehuss | @bors r+ p=1 | 2025-06-28T21:31:03 | 2025-06-28T21:31:03 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,067,964 | 143,163 | rustbot | r? @thomcc
rustbot has assigned @thomcc.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.
Use `r?` to explicitly pick a reviewer | 2025-06-28T21:41:34 | 2025-06-28T21:41:34 | {} | COLLABORATOR |
rust-lang | rust | 3,016,083,089 | 142,367 | GuillaumeGomez | @bors r=lolbinarycat rollup | 2025-06-28T21:58:28 | 2025-06-28T21:58:28 | {} | MEMBER |
rust-lang | rust | 3,016,083,116 | 142,367 | bors | :pushpin: Commit 1052ddda964811c25823aa7285595f7085392b36 has been approved by `lolbinarycat`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=lolbinarycat 1052ddda964811c25823aa7285595f7085392b36 -->
<!-- homu: {"type":"Approved","sha":"1052ddda964811c25823aa7285... | 2025-06-28T21:58:31 | 2025-06-28T21:58:31 | {} | COLLABORATOR |
rust-lang | rust | 3,015,995,291 | 142,693 | rust-timer | Awaiting bors try build completion.
@rustbot label: +S-waiting-on-perf
<!-- rust-timer: temporary --> | 2025-06-28T19:27:53 | 2025-06-28T23:24:09 | {} | COLLABORATOR |
rust-lang | rust | 3,016,145,105 | 142,693 | rust-timer | Finished benchmarking commit (6893bb554373e6438fbf77486be0a58c34e372d4): [comparison URL](https://perf.rust-lang.org/compare.html?start=7ba34c704529e7fcab80130c3fe40efe415d61b5&end=6893bb554373e6438fbf77486be0a58c34e372d4&stat=instructions:u).
### Overall result: ✅ improvements - no action needed
Benchmarking this p... | 2025-06-28T23:24:11 | 2025-06-28T23:24:11 | {} | COLLABORATOR |
rust-lang | rust | 3,016,150,345 | 143,118 | Kivooeo | The reason I'd think that this `b` thing adds a commit before to my PR is because when we do `git rebase -i head~N` (and yes I use lowercase for head, I just noticed every example is using uppercase) where N is more commits than I've made then It also includes them into my PR, and I have to do `git reflog` to find a co... | 2025-06-28T23:37:19 | 2025-06-28T23:37:19 | {} | MEMBER |
rust-lang | rust | 3,016,181,552 | 142,693 | fmease | r? compiler-errors or reassign if you're busy or not interested | 2025-06-29T00:23:51 | 2025-06-29T00:23:51 | {} | MEMBER |
rust-lang | rust | 3,016,079,443 | 143,157 | bors | :sunny: Try build successful - [checks-actions](https://github.com/rust-lang/rust/actions/runs/15947746278/job/44985470093)
Build commit: 32c9875b286c06d72c65a23eae833e6a27e2661d (`32c9875b286c06d72c65a23eae833e6a27e2661d`)
<!-- homu: {"type":"TryBuildCompleted","builders":{"checks-actions":"https://github.com/rust-lan... | 2025-06-28T21:49:50 | 2025-06-28T21:49:50 | {} | COLLABORATOR |
rust-lang | rust | 3,016,083,539 | 142,440 | tgross35 | Please split the renames to a separate commit as discussed in https://github.com/rust-lang/rust/pull/143118; six tests are losing their history here :(
(happy to do it for you if you get in a rebase rut) | 2025-06-28T21:59:40 | 2025-06-28T22:25:21 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,192,211 | 142,974 | cuviper | @bors r=Mark-Simulacrum | 2025-06-29T00:48:15 | 2025-06-29T00:48:15 | {} | MEMBER |
rust-lang | rust | 3,016,216,104 | 139,524 | bors | :umbrella: The latest upstream changes (presumably #143157) made this pull request unmergeable. Please [resolve the merge conflicts](https://rustc-dev-guide.rust-lang.org/git.html#rebasing-and-conflicts). | 2025-06-29T01:50:23 | 2025-06-29T01:50:23 | {} | COLLABORATOR |
rust-lang | rust | 3,016,219,031 | 143,138 | jdonszelmann | @bors rollup=always | 2025-06-29T01:59:27 | 2025-06-29T01:59:27 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,077,725 | 143,163 | rust-log-analyzer |
The job **`mingw-check-tidy`** failed! Check out the build log: [(web)](https://github.com/rust-lang/rust/actions/runs/15948441705/job/44985382425) [(plain)](https://github.com/rust-lang/rust/commit/148067d338db7aee66625e0f00082371ac5259a2/checks/44985382425/logs)
<details><summary><i>Click to see the possible cause ... | 2025-06-28T21:46:34 | 2025-06-28T22:44:57 | {} | COLLABORATOR |
rust-lang | rust | 3,016,035,564 | 142,902 | workingjubilee | > I don't think putting the package-lock.json (or package.json) file there would make sense, hence why I didn't do it. I'd love to make things simpler for everyone but currently it seems to not be possible or to be very ugly.
I do love beautiful solutions.
But I think "ugly but works", when the matter is at most an e... | 2025-06-28T21:17:28 | 2025-06-28T21:17:28 | {} | MEMBER |
rust-lang | rust | 3,016,103,857 | 143,162 | Jules-Bertholet | OTOH, this compiles:
```rust
unsafe extern "Rust" {
#[track_caller]
fn foo();
}
```
So perhaps we could argue that `track_caller` is part of the ABI-declared function signature… | 2025-06-28T22:33:24 | 2025-06-28T22:33:57 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,187,590 | 143,125 | cuviper | I'm not sure, but `aarch64-unknown-linux-gnu` *should* have neon, right?
So this PR should still think it `has_reliable_f16`? | 2025-06-29T00:36:46 | 2025-06-29T00:36:46 | {} | MEMBER |
rust-lang | rust | 3,016,198,178 | 143,169 | compiler-errors | @bors r+ | 2025-06-29T01:04:19 | 2025-06-29T01:04:19 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,077,633 | 143,161 | rust-log-analyzer |
The job **`mingw-check-2`** failed! Check out the build log: [(web)](https://github.com/rust-lang/rust/actions/runs/15948416648/job/44985319699) [(plain)](https://github.com/rust-lang/rust/commit/f8491b11f344222446a9bcd0c72b7bbb0834cdc0/checks/44985319699/logs)
<details><summary><i>Click to see the possible cause of ... | 2025-06-28T21:46:20 | 2025-06-28T21:50:13 | {} | COLLABORATOR |
rust-lang | rust | 3,016,079,633 | 143,157 | matthiaskrgr | @bors r+ rollup=never p=5 | 2025-06-28T21:50:20 | 2025-06-28T21:50:20 | {} | MEMBER |
rust-lang | rust | 3,016,118,358 | 143,118 | Kivooeo | I'm doing `git rebase -i head~N` pretty often to be clear, for exapmple for squash all commits, just edit one single commit to fix some nits, or even just rename commit
But this one sounds more complex than such small fixes, if for a person who knows git well it might be an easy task, but for me it's more like a str... | 2025-06-28T22:42:52 | 2025-06-28T22:42:52 | {} | MEMBER |
rust-lang | rust | 3,016,136,830 | 143,169 | rustbot | Some changes occurred in compiler/rustc_codegen_gcc
cc @antoyo, @GuillaumeGomez
`rustc_error_messages` was changed
cc @davidtwco, @compiler-errors, @TaKO8Ki | 2025-06-28T23:03:09 | 2025-06-28T23:03:09 | {} | COLLABORATOR |
rust-lang | rust | 3,016,152,766 | 143,161 | bors | :pushpin: Commit 3dcbc1e5bcddfade60a459caad642fd8c37e8f68 has been approved by `GuillaumeGomez`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=GuillaumeGomez 3dcbc1e5bcddfade60a459caad642fd8c37e8f68 -->
<!-- homu: {"type":"Approved","sha":"3dcbc1e5bcddfade60a459... | 2025-06-28T23:41:41 | 2025-06-28T23:41:41 | {} | COLLABORATOR |
rust-lang | rust | 3,016,175,603 | 143,118 | Kivooeo | Thanks! | 2025-06-29T00:12:31 | 2025-06-29T00:12:31 | {
"heart": 1
} | MEMBER |
rust-lang | rust | 3,016,192,232 | 142,974 | bors | :pushpin: Commit c62c9d5d8c23f6e24cde10fb6cbea567fffe9c42 has been approved by `Mark-Simulacrum`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=Mark-Simulacrum c62c9d5d8c23f6e24cde10fb6cbea567fffe9c42 -->
<!-- homu: {"type":"Approved","sha":"c62c9d5d8c23f6e24cde... | 2025-06-29T00:48:18 | 2025-06-29T00:48:18 | {} | COLLABORATOR |
rust-lang | rust | 3,016,199,756 | 143,163 | workingjubilee | @PixelDust22 Adding the getter function is a new API. | 2025-06-29T01:08:25 | 2025-06-29T01:08:25 | {} | MEMBER |
rust-lang | rust | 3,016,199,972 | 143,163 | workingjubilee | The change in #134143 was instantly stable because there was no way to feature flag replacing a struct with an enum. Adding a trivial function, however, is something that can be done under a feature flag. Usually doing so is just a formality, but it needs an FCP to add it as stable API in any case. | 2025-06-29T01:09:10 | 2025-06-29T01:11:44 | {} | MEMBER |
rust-lang | rust | 3,016,071,474 | 143,155 | GuillaumeGomez | Thanks! :rofl:
@bors r+ rollup | 2025-06-28T21:42:18 | 2025-06-28T21:42:18 | {} | MEMBER |
rust-lang | rust | 3,016,077,262 | 143,163 | workingjubilee | r? libs-api | 2025-06-28T21:45:28 | 2025-06-28T21:45:28 | {} | MEMBER |
rust-lang | rust | 3,016,192,191 | 142,625 | rust-timer | Finished benchmarking commit (11ad40bb839ca16f74784b4ab72596ad85587298): [comparison URL](https://perf.rust-lang.org/compare.html?start=7ba34c704529e7fcab80130c3fe40efe415d61b5&end=11ad40bb839ca16f74784b4ab72596ad85587298&stat=instructions:u).
### Overall result: ❌✅ regressions and improvements - please read the text ... | 2025-06-29T00:48:12 | 2025-06-29T00:48:12 | {} | COLLABORATOR |
rust-lang | rust | 3,016,030,204 | 143,156 | rustbot | Some changes occurred in compiler/rustc_codegen_ssa
cc @WaffleLapkin
Some changes occurred in compiler/rustc_codegen_ssa/src/codegen_attrs.rs
cc @jdonszelmann | 2025-06-28T21:05:23 | 2025-06-28T21:05:23 | {} | COLLABORATOR |
rust-lang | rust | 3,016,092,764 | 143,157 | bors | :hourglass: Testing commit a62de822fa254bb062a9f927c00d7cc82580d8e4 with merge cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c...
<!-- homu: {"type":"BuildStarted","head_sha":"a62de822fa254bb062a9f927c00d7cc82580d8e4","merge_sha":"cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c"} --> | 2025-06-28T22:13:45 | 2025-06-28T22:13:45 | {} | COLLABORATOR |
rust-lang | rust | 3,016,118,543 | 143,164 | workingjubilee | Regression arises from https://github.com/rust-lang/rust/pull/137268
I notice in that crater run there were an unusually high number of `error -> error` cases for a crater... | 2025-06-28T22:43:23 | 2025-06-28T22:43:32 | {} | MEMBER |
rust-lang | rust | 3,016,083,201 | 142,693 | rust-timer | Queued 6893bb554373e6438fbf77486be0a58c34e372d4 with parent 7ba34c704529e7fcab80130c3fe40efe415d61b5, future [comparison URL](https://perf.rust-lang.org/compare.html?start=7ba34c704529e7fcab80130c3fe40efe415d61b5&end=6893bb554373e6438fbf77486be0a58c34e372d4).
There are currently 0 preceding artifacts in the [queue](htt... | 2025-06-28T21:58:43 | 2025-06-28T23:24:09 | {} | COLLABORATOR |
rust-lang | rust | 3,016,144,859 | 143,169 | rust-log-analyzer |
The job **`x86_64-gnu-llvm-19`** failed! Check out the build log: [(web)](https://github.com/rust-lang/rust/actions/runs/15949019464/job/44986574018) [(plain)](https://github.com/rust-lang/rust/commit/492e04e80bf48456f77938b8591a5fce01cebd6a/checks/44986574018/logs)
<details><summary><i>Click to see the possible caus... | 2025-06-28T23:23:09 | 2025-06-28T23:36:59 | {} | COLLABORATOR |
rust-lang | rust | 3,016,147,572 | 143,168 | rust-log-analyzer |
The job **`aarch64-gnu-llvm-19-1`** failed! Check out the build log: [(web)](https://github.com/rust-lang/rust/actions/runs/15948898692/job/44986324463) [(plain)](https://github.com/rust-lang/rust/commit/15192535c6eaad02ae8216d9bbd78c910483e5ee/checks/44986324463/logs)
<details><summary><i>Click to see the possible c... | 2025-06-28T23:30:00 | 2025-06-28T23:42:04 | {} | COLLABORATOR |
rust-lang | rust | 3,016,198,197 | 143,169 | bors | :pushpin: Commit 8429c9911b68afe9c0cc5804cb15fc22f03d913c has been approved by `compiler-errors`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=compiler-errors 8429c9911b68afe9c0cc5804cb15fc22f03d913c -->
<!-- homu: {"type":"Approved","sha":"8429c9911b68afe9c0cc... | 2025-06-29T01:04:22 | 2025-06-29T01:04:22 | {} | COLLABORATOR |
rust-lang | rust | 3,016,057,808 | 143,160 | bors | :pushpin: Commit e0c8c3fbb049b278c286d7efd9ca90fe14763f32 has been approved by `ehuss`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=ehuss e0c8c3fbb049b278c286d7efd9ca90fe14763f32 -->
<!-- homu: {"type":"Approved","sha":"e0c8c3fbb049b278c286d7efd9ca90fe14763f32... | 2025-06-28T21:31:06 | 2025-06-28T21:31:06 | {} | COLLABORATOR |
rust-lang | rust | 3,016,063,395 | 142,902 | GuillaumeGomez | > But I think "ugly but works", when the matter is at most an extra few files of no significant size, is better than "reinventing the incredible complexities of dependency management in an ad hoc manner, strewn across completely unrelated parts of the codebase".
Agreed, hence why I suggested to only run JS checks if a... | 2025-06-28T21:35:20 | 2025-06-28T21:35:20 | {} | MEMBER |
rust-lang | rust | 3,016,093,447 | 142,625 | github-actions[bot] | <details>
<summary>What is this?</summary>
This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.
</details>
Comparing 7ba34c704529e7fcab80130c3fe40efe415d61b5 (parent) -> 11ad40bb839ca16f74784b4ab72596ad85587298 (this PR)
# Test difference... | 2025-06-28T22:15:31 | 2025-06-28T22:15:31 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,100,896 | 143,162 | Jules-Bertholet | Yes. But it’s not clear what the correct behavior should be. Should the unmangled, exported symbol correspond to the caller-tracking function, or the non-tracking shim? | 2025-06-28T22:29:10 | 2025-06-28T22:29:20 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,175,043 | 143,118 | tgross35 | Pushed! Basically exactly https://github.com/rust-lang/rust/pull/143118#issuecomment-3014663927 for reference.
(I'll help with the rest tomorrow, going offline for the day) | 2025-06-29T00:11:30 | 2025-06-29T00:11:30 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,056,153 | 142,310 | workingjubilee | @nikic as usual is off being a gentleman and a scholar and has opened https://github.com/llvm/llvm-project/pull/144673 | 2025-06-28T21:26:14 | 2025-06-28T21:26:14 | {} | MEMBER |
rust-lang | rust | 3,016,064,322 | 143,161 | rustbot | Some changes occurred in compiler/rustc_codegen_gcc
cc @antoyo, @GuillaumeGomez | 2025-06-28T21:38:07 | 2025-06-28T21:38:07 | {} | COLLABORATOR |
rust-lang | rust | 3,016,097,746 | 143,162 | workingjubilee | I believe this is because `#[track_caller]` secretly materializes secondary functions to call them with a modified ABI, and it is attempting to propagate the function attributes like `no_mangle`. | 2025-06-28T22:23:31 | 2025-06-28T22:29:19 | {} | MEMBER |
rust-lang | rust | 3,016,104,917 | 143,118 | Kivooeo | (I will read the explanation after I send this message so I'm just trying to explain what goes wrong when I tried to make it)
> If you are having rebase problems, I'm happy to do the fix and push your branch - just ask :) but where did you get stuck?
I stucked on a very first step
```
git rebase -i master --keep-... | 2025-06-28T22:35:35 | 2025-06-28T22:35:35 | {} | MEMBER |
rust-lang | rust | 3,016,105,716 | 143,162 | workingjubilee | I think we should take `#[unsafe(no_mangle)]` and `#[track_caller]` being allowed at the same time by HIR attribute checking, yet not working, as evidence that It's Not That Deep, people just didn't think about it.
But I invite you to actually separately compile a library that would *use* `track_caller` and report bac... | 2025-06-28T22:37:05 | 2025-06-28T22:37:31 | {} | MEMBER |
rust-lang | rust | 3,016,137,126 | 142,974 | bors | :hourglass: Trying commit c62c9d5d8c23f6e24cde10fb6cbea567fffe9c42 with merge 3869fe1b678ab9c62e9813e79e7670d89549c9ce...
<!-- homu: {"type":"TryBuildStarted","head_sha":"c62c9d5d8c23f6e24cde10fb6cbea567fffe9c42","merge_sha":"3869fe1b678ab9c62e9813e79e7670d89549c9ce"} --> | 2025-06-28T23:04:00 | 2025-06-28T23:04:00 | {} | COLLABORATOR |
rust-lang | rust | 3,016,137,585 | 143,169 | bors | :pushpin: Commit 492e04e80bf48456f77938b8591a5fce01cebd6a has been approved by `compiler-errors`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=compiler-errors 492e04e80bf48456f77938b8591a5fce01cebd6a -->
<!-- homu: {"type":"Approved","sha":"492e04e80bf48456f779... | 2025-06-28T23:05:17 | 2025-06-28T23:05:17 | {} | COLLABORATOR |
rust-lang | rust | 3,016,146,592 | 143,118 | tgross35 | For any git thing there are 1000 ways to get the same results 😆 I'm happy to help you get there, but I'm also happy to do it for you because I know this kind of thing is tricky and we certainly don't expect all contributors to know git like the back of their hand.
> I stucked on a very first step
>
> ```
> git ... | 2025-06-28T23:28:50 | 2025-06-28T23:28:50 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,152,749 | 143,161 | antoyo | @bors r=GuillaumeGomez p=1 | 2025-06-28T23:41:38 | 2025-06-28T23:41:38 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,191,529 | 142,974 | bors | :sunny: Try build successful - [checks-actions](https://github.com/rust-lang/rust/actions/runs/15949026838/job/44988317201)
Build commit: 3869fe1b678ab9c62e9813e79e7670d89549c9ce (`3869fe1b678ab9c62e9813e79e7670d89549c9ce`)
<!-- homu: {"type":"TryBuildCompleted","builders":{"checks-actions":"https://github.com/rust-lan... | 2025-06-29T00:46:28 | 2025-06-29T00:46:28 | {} | COLLABORATOR |
rust-lang | rust | 3,016,203,859 | 143,157 | github-actions[bot] | <details>
<summary>What is this?</summary>
This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.
</details>
Comparing 11ad40bb839ca16f74784b4ab72596ad85587298 (parent) -> cf38b8e663f15db10ce49d7bbce02c99fc3dbc0c (this PR)
# Test difference... | 2025-06-29T01:18:13 | 2025-06-29T01:18:13 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,065,085 | 142,902 | GuillaumeGomez | Ah my bad, then reassigning @lolbinarycat (please write a message so people not involved in conversation understand what's going on 😆 ). | 2025-06-28T21:39:51 | 2025-06-28T21:39:51 | {
"+1": 1
} | MEMBER |
rust-lang | rust | 3,016,082,048 | 143,137 | RalfJung | @bors2 try jobs=dist-riscv64-linux | 2025-06-28T21:55:57 | 2025-06-28T21:55:57 | {} | MEMBER |
rust-lang | rust | 3,016,105,133 | 143,161 | bors | :v: @antoyo, you can now approve this pull request!
If @GuillaumeGomez told you to "`r=me`" after making some further change, please make that change, then do `@bors r=@GuillaumeGomez`
<!-- homu: {"type":"Delegated","delegator":"GuillaumeGomez","delegate":"antoyo"} --> | 2025-06-28T22:36:20 | 2025-06-28T22:36:20 | {} | COLLABORATOR |
rust-lang | rust | 3,016,158,298 | 143,075 | JayAndJef | I was wondering why my kernel couldn't compile yet x86_64 expected a return type of `!` for interrupt handlers! good to know there's a fix coming. | 2025-06-28T23:54:47 | 2025-06-28T23:54:47 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,203,736 | 143,157 | rust-timer | 📌 Perf builds for each rolled up PR:
| PR# | Message | Perf Build Sha |
|----|----|:-----:|
|#123476|std::net: adding `unix_socket_exclbind` feature for solaris…|`032878f28b0461a6a4e678ccb056147b184cb5ef` ([link](https://github.com/rust-lang/rust/commit/032878f28b0461a6a4e678ccb056147b184cb5ef))|
|#142708|Do not incl... | 2025-06-29T01:17:46 | 2025-06-29T01:17:46 | {} | COLLABORATOR |
rust-lang | rust | 3,016,034,598 | 142,974 | bors | :broken_heart: Test failed - [checks-actions](https://github.com/rust-lang/rust/actions/runs/15947660506/job/44984963949)
<!-- homu: {"type":"TryBuildFailed","builder_url":"https://github.com/rust-lang/rust/actions/runs/15947660506/job/44984963949","builder_name":"checks-actions"} --> | 2025-06-28T21:15:34 | 2025-06-28T21:15:34 | {} | COLLABORATOR |
rust-lang | rust | 3,016,071,518 | 143,155 | bors | :pushpin: Commit 581cb1100ece356ff133a58bac8ce855f38bc432 has been approved by `GuillaumeGomez`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=GuillaumeGomez 581cb1100ece356ff133a58bac8ce855f38bc432 -->
<!-- homu: {"type":"Approved","sha":"581cb1100ece356ff133a5... | 2025-06-28T21:42:21 | 2025-06-28T21:42:21 | {} | COLLABORATOR |
rust-lang | rust | 3,016,079,642 | 143,157 | bors | :pushpin: Commit a62de822fa254bb062a9f927c00d7cc82580d8e4 has been approved by `matthiaskrgr`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=matthiaskrgr a62de822fa254bb062a9f927c00d7cc82580d8e4 -->
<!-- homu: {"type":"Approved","sha":"a62de822fa254bb062a9f927c0... | 2025-06-28T21:50:22 | 2025-06-28T21:50:22 | {} | COLLABORATOR |
rust-lang | rust | 3,016,095,836 | 143,161 | antoyo | Are we doing something seriously wrong with our subtree syncs? This [commit](https://github.com/rust-lang/rust/pull/143161/commits/a420d39afb992093bd0105aecfa033a640115c0a) was already done in the subtree [here](https://github.com/rust-lang/rustc_codegen_gcc/commit/144989400e64298805690dc923f50a97fbf41c9d#diff-e4f794ca... | 2025-06-28T22:19:09 | 2025-06-28T22:19:09 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,100,593 | 143,166 | rustbot | r? @thomcc
rustbot has assigned @thomcc.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.
Use `r?` to explicitly pick a reviewer | 2025-06-28T22:28:20 | 2025-06-28T22:28:20 | {} | COLLABORATOR |
rust-lang | rust | 3,016,112,857 | 143,167 | rust-bors[bot] | :hourglass: Trying commit 05dc1749b967bba86fb3f8ec0247e9886a511f63 with merge 209ede66b6181c8fa07f95666d9f6fe887e054b2…
To cancel the try build, run the command `@bors2 try cancel`.
| 2025-06-28T22:40:19 | 2025-06-28T22:40:19 | {} | CONTRIBUTOR |
rust-lang | rust | 3,016,197,961 | 143,171 | bors | :pushpin: Commit 7a55709baf9c0c4b99957f67d8f0b42a22daa047 has been approved by `compiler-errors`
It is now in the [queue](https://bors.rust-lang.org/homu/queue/rust) for this repository.
<!-- @bors r=compiler-errors 7a55709baf9c0c4b99957f67d8f0b42a22daa047 -->
<!-- homu: {"type":"Approved","sha":"7a55709baf9c0c4b9995... | 2025-06-29T01:03:36 | 2025-06-29T01:03:36 | {} | COLLABORATOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.