Rework MIR inlining debuginfo so function parameters show up in debuggers. #128861

khuey · 2024-08-09T03:11:15Z

Line numbers of multiply-inlined functions were fixed in #114643 by using a single DISubprogram. That, however, triggered assertions because parameters weren't deduplicated. The "solution" to that in #115417 was to insert a DILexicalScope below the DISubprogram and parent all of the parameters to that scope. That fixed the assertion, but debuggers (including gdb and lldb) don't recognize variables that are not parented to the subprogram itself as parameters, even if they are emitted with DW_TAG_formal_parameter.

Consider the program:

use std::env;

#[inline(always)]
fn square(n: i32) -> i32 {
    n * n
}

#[inline(never)]
fn square_no_inline(n: i32) -> i32 {
    n * n
}

fn main() {
    let x = square(env::vars().count() as i32);
    let y = square_no_inline(env::vars().count() as i32);
    println!("{x} == {y}");
}

When making a release build with debug=2 and rustc 1.82.0-nightly (8b38707 2024-08-07)

(gdb) r
Starting program: /ephemeral/tmp/target/release/tmp [Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, tmp::square () at src/main.rs:5
5	    n * n
(gdb) info args
No arguments.
(gdb) info locals
n = 31
(gdb) c
Continuing.

Breakpoint 2, tmp::square_no_inline (n=31) at src/main.rs:10
10	    n * n
(gdb) info args
n = 31
(gdb) info locals
No locals.

This issue is particularly annoying because it removes arguments from stack traces.

The DWARF for the inlined function looks like this:

< 2><0x00002132 GOFF=0x00002132>      DW_TAG_subprogram
                                        DW_AT_linkage_name          _ZN3tmp6square17hc507052ff3d2a488E
                                        DW_AT_name                  square
                                        DW_AT_decl_file             0x0000000f /ephemeral/tmp/src/main.rs
                                        DW_AT_decl_line             0x00000004
                                        DW_AT_type                  0x00001a56<.debug_info+0x00001a56>
                                        DW_AT_inline                DW_INL_inlined
< 3><0x00002142 GOFF=0x00002142>        DW_TAG_lexical_block
< 4><0x00002143 GOFF=0x00002143>          DW_TAG_formal_parameter
                                            DW_AT_name                  n
                                            DW_AT_decl_file             0x0000000f /ephemeral/tmp/src/main.rs
                                            DW_AT_decl_line             0x00000004
                                            DW_AT_type                  0x00001a56<.debug_info+0x00001a56>
< 4><0x0000214e GOFF=0x0000214e>          DW_TAG_null
< 3><0x0000214f GOFF=0x0000214f>        DW_TAG_null

That DW_TAG_lexical_block inhibits every debugger I've tested from recognizing 'n' as a parameter.

This patch removes the additional lexical scope. Parameters can be easily deduplicated by a tuple of their scope and the argument index, at the trivial cost of taking a Hash + Eq bound on DIScope.

rustbot · 2024-08-09T03:11:23Z

r? @Nadrieril

rustbot has assigned @Nadrieril.
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

khuey · 2024-08-09T03:11:56Z

r? @dpaoliello

rustbot · 2024-08-09T03:11:59Z

Failed to set assignee to dpaoliello: invalid assignee

Note: Only org members with at least the repository "read" role, users with write permissions, or people who have commented on the PR may be assigned.

khuey · 2024-08-09T03:12:54Z

r? @wesleywiser

wesleywiser · 2024-08-12T15:13:50Z

Thanks @khuey! The example you gave in the PR description was super helpful in understanding the issue and your fix 🥇

@bors r+

bors · 2024-08-12T15:13:53Z

📌 Commit 0e4136b has been approved by wesleywiser

It is now in the queue for this repository.

…ginfo, r=wesleywiser Rework MIR inlining debuginfo so function parameters show up in debuggers. Line numbers of multiply-inlined functions were fixed in rust-lang#114643 by using a single DISubprogram. That, however, triggered assertions because parameters weren't deduplicated. The "solution" to that in rust-lang#115417 was to insert a DILexicalScope below the DISubprogram and parent all of the parameters to that scope. That fixed the assertion, but debuggers (including gdb and lldb) don't recognize variables that are not parented to the subprogram itself as parameters, even if they are emitted with DW_TAG_formal_parameter. Consider the program: ```rust use std::env; #[inline(always)] fn square(n: i32) -> i32 { n * n } #[inline(never)] fn square_no_inline(n: i32) -> i32 { n * n } fn main() { let x = square(env::vars().count() as i32); let y = square_no_inline(env::vars().count() as i32); println!("{x} == {y}"); } ``` When making a release build with debug=2 and rustc 1.82.0-nightly (8b38707 2024-08-07) ``` (gdb) r Starting program: /ephemeral/tmp/target/release/tmp [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Breakpoint 1, tmp::square () at src/main.rs:5 5 n * n (gdb) info args No arguments. (gdb) info locals n = 31 (gdb) c Continuing. Breakpoint 2, tmp::square_no_inline (n=31) at src/main.rs:10 10 n * n (gdb) info args n = 31 (gdb) info locals No locals. ``` This issue is particularly annoying because it removes arguments from stack traces. The DWARF for the inlined function looks like this: ``` < 2><0x00002132 GOFF=0x00002132> DW_TAG_subprogram DW_AT_linkage_name _ZN3tmp6square17hc507052ff3d2a488E DW_AT_name square DW_AT_decl_file 0x0000000f /ephemeral/tmp/src/main.rs DW_AT_decl_line 0x00000004 DW_AT_type 0x00001a56<.debug_info+0x00001a56> DW_AT_inline DW_INL_inlined < 3><0x00002142 GOFF=0x00002142> DW_TAG_lexical_block < 4><0x00002143 GOFF=0x00002143> DW_TAG_formal_parameter DW_AT_name n DW_AT_decl_file 0x0000000f /ephemeral/tmp/src/main.rs DW_AT_decl_line 0x00000004 DW_AT_type 0x00001a56<.debug_info+0x00001a56> < 4><0x0000214e GOFF=0x0000214e> DW_TAG_null < 3><0x0000214f GOFF=0x0000214f> DW_TAG_null ``` That DW_TAG_lexical_block inhibits every debugger I've tested from recognizing 'n' as a parameter. This patch removes the additional lexical scope. Parameters can be easily deduplicated by a tuple of their scope and the argument index, at the trivial cost of taking a Hash + Eq bound on DIScope.

…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#128712 (Normalize struct tail properly for `dyn` ptr-to-ptr casting in new solver) - rust-lang#128861 (Rework MIR inlining debuginfo so function parameters show up in debuggers.) - rust-lang#128912 (Store `do_not_recommend`-ness in impl header) - rust-lang#129000 (bootstrap: clear miri ui-test deps when miri sysroot gets rebuilt) - rust-lang#129013 (Remove unused script from run-make tests) - rust-lang#129017 (Replace `std::fmt:FormatterFn` with `std::fmt::from_fn`) Failed merges: - rust-lang#128935 (More work on `zstd` compression) r? `@ghost` `@rustbot` modify labels: rollup

matthiaskrgr · 2024-08-12T21:10:26Z

@bors r-
#129022 (comment)

khuey · 2024-08-12T21:19:39Z

Looks like arguments with MSVC don't have the arg field set on the DILocalVariable. Not sure whether that's a bug, but I'll adjust the FileCheck annotations for now.

khuey · 2024-08-12T21:27:54Z

Would be good if someone could make bors try that.

cjgillot · 2024-08-12T22:08:47Z

Cc @saethlin as you've been working on debuginfo recently.

saethlin · 2024-08-12T22:30:46Z

Would be good if someone could make bors try that.

I can make that happen for you once mingw-check-tidy passes.

rust-log-analyzer · 2024-08-14T22:29:30Z

The job x86_64-fuchsia failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[22:25:14.738] Wait for 1m4s before next attempt...: Cloning https://chromium.googlesource.com/chromium/deps/icu

[22:25:14.896] Wait for 1m4s before next attempt...: Cloning https://chromium.googlesource.com/chromium/deps/icu

ERROR: 'git clone --no-checkout --filter=blob:none https://chromium.googlesource.com/chromium/deps/icu /checkout/obj/fuchsia/third_party/icu/default' failed:

stderr:
Cloning into '/checkout/obj/fuchsia/third_party/icu/default'...
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
---
command fail error: exit status 128

[22:26:48.986] Wait for 1m4s before next attempt...: Cloning https://chromium.googlesource.com/chromium/deps/icu

ERROR: 'git clone --no-checkout --filter=blob:none https://chromium.googlesource.com/chromium/deps/icu /checkout/obj/fuchsia/third_party/icu/default' failed:

stderr:
Cloning into '/checkout/obj/fuchsia/third_party/icu/default'...
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
---
[22:27:52.986] Attempt 3/3: Cloning https://chromium.googlesource.com/chromium/deps/icu

[22:27:53.072] Attempt 3/3: Cloning https://chromium.googlesource.com/chromium/deps/icu

[22:28:23.206] Jiri packages are not fetched due to fatal errors when updating projects.
[22:28:23.206] Jiri hooks are not run due to fatal errors when updating projects or packages
ERROR: Creating project "chromium/deps/icu@latest": "Cloning https://chromium.googlesource.com/chromium/deps/icu" failed 3 times in a row, Last error: 'git clone --no-checkout --filter=blob:none https://chromium.googlesource.com/chromium/deps/icu /checkout/obj/fuchsia/third_party/icu/latest' failed:

stderr:
Cloning into '/checkout/obj/fuchsia/third_party/icu/latest'...
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
fatal: expected flush after ref listing

command fail error: exit status 128
Creating project "chromium/deps/icu@default": "Cloning https://chromium.googlesource.com/chromium/deps/icu" failed 3 times in a row, Last error: 'git clone --no-checkout --filter=blob:none https://chromium.googlesource.com/chromium/deps/icu /checkout/obj/fuchsia/third_party/icu/default' failed:

stderr:
Cloning into '/checkout/obj/fuchsia/third_party/icu/default'...
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503

bors · 2024-08-14T22:30:13Z

💔 Test failed - checks-actions

saethlin · 2024-08-14T22:57:17Z

Fuchsia infra problem maybe? https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/.E2.9C.94.20Are.20fuchsia.20CI.20jobs.20broken.3F/near/462428061

@bors retry

…nfo, r=wesleywiser Rework MIR inlining debuginfo so function parameters show up in debuggers. Line numbers of multiply-inlined functions were fixed in rust-lang#114643 by using a single DISubprogram. That, however, triggered assertions because parameters weren't deduplicated. The "solution" to that in rust-lang#115417 was to insert a DILexicalScope below the DISubprogram and parent all of the parameters to that scope. That fixed the assertion, but debuggers (including gdb and lldb) don't recognize variables that are not parented to the subprogram itself as parameters, even if they are emitted with DW_TAG_formal_parameter. Consider the program: ```rust use std::env; #[inline(always)] fn square(n: i32) -> i32 { n * n } #[inline(never)] fn square_no_inline(n: i32) -> i32 { n * n } fn main() { let x = square(env::vars().count() as i32); let y = square_no_inline(env::vars().count() as i32); println!("{x} == {y}"); } ``` When making a release build with debug=2 and rustc 1.82.0-nightly (8b38707 2024-08-07) ``` (gdb) r Starting program: /ephemeral/tmp/target/release/tmp [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Breakpoint 1, tmp::square () at src/main.rs:5 5 n * n (gdb) info args No arguments. (gdb) info locals n = 31 (gdb) c Continuing. Breakpoint 2, tmp::square_no_inline (n=31) at src/main.rs:10 10 n * n (gdb) info args n = 31 (gdb) info locals No locals. ``` This issue is particularly annoying because it removes arguments from stack traces. The DWARF for the inlined function looks like this: ``` < 2><0x00002132 GOFF=0x00002132> DW_TAG_subprogram DW_AT_linkage_name _ZN3tmp6square17hc507052ff3d2a488E DW_AT_name square DW_AT_decl_file 0x0000000f /ephemeral/tmp/src/main.rs DW_AT_decl_line 0x00000004 DW_AT_type 0x00001a56<.debug_info+0x00001a56> DW_AT_inline DW_INL_inlined < 3><0x00002142 GOFF=0x00002142> DW_TAG_lexical_block < 4><0x00002143 GOFF=0x00002143> DW_TAG_formal_parameter DW_AT_name n DW_AT_decl_file 0x0000000f /ephemeral/tmp/src/main.rs DW_AT_decl_line 0x00000004 DW_AT_type 0x00001a56<.debug_info+0x00001a56> < 4><0x0000214e GOFF=0x0000214e> DW_TAG_null < 3><0x0000214f GOFF=0x0000214f> DW_TAG_null ``` That DW_TAG_lexical_block inhibits every debugger I've tested from recognizing 'n' as a parameter. This patch removes the additional lexical scope. Parameters can be easily deduplicated by a tuple of their scope and the argument index, at the trivial cost of taking a Hash + Eq bound on DIScope.

bors · 2024-08-14T23:47:25Z

⌛ Testing commit 1c5e3c9 with merge ffd6a66...

rust-log-analyzer · 2024-08-15T00:27:48Z

The job x86_64-mingw failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[107/128] Building CXX object MachO/CMakeFiles/lldMachO.dir/UnwindInfoSection.cpp.obj
[108/128] Building CXX object MachO/CMakeFiles/lldMachO.dir/Writer.cpp.obj
[109/128] Building CXX object MinGW/CMakeFiles/lldMinGW.dir/Driver.cpp.obj
[110/128] Linking CXX static library lib\liblldMinGW.a
FAILED: lib/liblldMinGW.a 
C:\Windows\system32\cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E rm -f lib\liblldMinGW.a && C:\a\rust\rust\mingw64\bin\ar.exe qc lib\liblldMinGW.a  MinGW/CMakeFiles/lldMinGW.dir/Driver.cpp.obj && C:\a\rust\rust\mingw64\bin\ranlib.exe lib\liblldMinGW.a && cd ."
C:\a\rust\rust\mingw64\bin\ar.exe: could not create temporary file whilst writing archive: no more archived files
[111/128] Linking CXX static library lib\liblldMachO.a
[112/128] Building CXX object wasm/CMakeFiles/lldWasm.dir/Driver.cpp.obj
[113/128] Building CXX object wasm/CMakeFiles/lldWasm.dir/InputFiles.cpp.obj
[114/128] Building CXX object wasm/CMakeFiles/lldWasm.dir/InputChunks.cpp.obj

bors · 2024-08-15T00:28:28Z

💔 Test failed - checks-actions

khuey · 2024-08-15T03:44:21Z

That also looks like it's unrelated to this patch.

jieyouxu · 2024-08-15T03:58:16Z

2024-08-15T00:27:34.6712215Z FAILED: lib/liblldMinGW.a 
2024-08-15T00:27:35.0246237Z C:\Windows\system32\cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E rm -f lib\liblldMinGW.a && C:\a\rust\rust\mingw64\bin\ar.exe qc lib\liblldMinGW.a  MinGW/CMakeFiles/lldMinGW.dir/Driver.cpp.obj && C:\a\rust\rust\mingw64\bin\ranlib.exe lib\liblldMinGW.a && cd ."
2024-08-15T00:27:35.0248405Z C:\a\rust\rust\mingw64\bin\ar.exe: could not create temporary file whilst writing archive: no more archived files

@bors retry (looks unrelated to this PR)

bors · 2024-08-15T11:42:18Z

⌛ Testing commit 1c5e3c9 with merge 3139ff0...

bors · 2024-08-15T14:12:44Z

☀️ Test successful - checks-actions
Approved by: wesleywiser
Pushing 3139ff0 to master...

rust-timer · 2024-08-15T18:30:12Z

Finished benchmarking commit (3139ff0): comparison URL.

Overall result: ❌✅ regressions and improvements - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.3%	[2.3%, 2.3%]	1
Improvements ✅ (primary)	-1.2%	[-1.4%, -1.1%]	6
Improvements ✅ (secondary)	-1.2%	[-1.3%, -1.2%]	2
All ❌✅ (primary)	-1.2%	[-1.4%, -1.1%]	6

Max RSS (memory usage)

Results (primary -2.9%, secondary 3.2%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	3.2%	[2.8%, 3.5%]	3
Improvements ✅ (primary)	-2.9%	[-4.1%, -2.1%]	4
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-2.9%	[-4.1%, -2.1%]	4

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

Results (primary -2.7%, secondary -1.5%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-2.7%	[-6.5%, -0.1%]	80
Improvements ✅ (secondary)	-1.5%	[-3.7%, -0.6%]	21
All ❌✅ (primary)	-2.7%	[-6.5%, -0.1%]	80

Bootstrap: 753.275s -> 751.489s (-0.24%)
Artifact size: 339.20 MiB -> 339.19 MiB (-0.00%)

Kobzol · 2024-08-15T18:33:09Z

More improvements than regressions. And awesome binary size wins!

@rustbot label: +perf-regression-triaged

nnethercote · 2024-08-15T22:15:41Z

This makes me wonder if there are any other debuginfo inefficiencies that could be fixed...

khuey · 2024-08-15T22:31:51Z

This makes me wonder if there are any other debuginfo inefficiencies that could be fixed...

There are a lot.

rustbot assigned Nadrieril Aug 9, 2024

rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Aug 9, 2024

rustbot assigned wesleywiser and unassigned Nadrieril Aug 9, 2024

jieyouxu added the A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.) label Aug 9, 2024

khuey force-pushed the mir-inlining-parameters-debuginfo branch from 2746cc4 to 0e4136b Compare August 9, 2024 12:41

dpaoliello approved these changes Aug 9, 2024

View reviewed changes

wesleywiser approved these changes Aug 12, 2024

View reviewed changes

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 12, 2024

matthiaskrgr mentioned this pull request Aug 12, 2024

Rollup of 7 pull requests #129012

Closed

matthiaskrgr mentioned this pull request Aug 12, 2024

Rollup of 6 pull requests #129022

Closed

bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 12, 2024

This comment has been minimized.

Sign in to view

bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 14, 2024

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 14, 2024

bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 15, 2024

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 15, 2024

bors added the merged-by-bors This PR was explicitly merged by bors. label Aug 15, 2024

bors merged commit 3139ff0 into rust-lang:master Aug 15, 2024
7 checks passed

rustbot added this to the 1.82.0 milestone Aug 15, 2024

rustbot added the perf-regression Performance regression. label Aug 15, 2024

rustbot added the perf-regression-triaged The performance regression has been triaged. label Aug 15, 2024

saethlin mentioned this pull request Aug 17, 2024

LLVM debuginfo assertion "overlapping or duplicate fragments" fails with ridiculous MIR inlining #129206

Open

khuey mentioned this pull request Aug 29, 2024

Large amounts of repeated data in debug info #129722

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Rework MIR inlining debuginfo so function parameters show up in debuggers. #128861

Rework MIR inlining debuginfo so function parameters show up in debuggers. #128861

khuey commented Aug 9, 2024 •

edited by saethlin

Loading

rustbot commented Aug 9, 2024

khuey commented Aug 9, 2024

rustbot commented Aug 9, 2024

khuey commented Aug 9, 2024

wesleywiser commented Aug 12, 2024

bors commented Aug 12, 2024

matthiaskrgr commented Aug 12, 2024

khuey commented Aug 12, 2024

khuey commented Aug 12, 2024

This comment has been minimized.

cjgillot commented Aug 12, 2024

saethlin commented Aug 12, 2024

rust-log-analyzer commented Aug 14, 2024

bors commented Aug 14, 2024

saethlin commented Aug 14, 2024

bors commented Aug 14, 2024

rust-log-analyzer commented Aug 15, 2024

bors commented Aug 15, 2024

khuey commented Aug 15, 2024

jieyouxu commented Aug 15, 2024

bors commented Aug 15, 2024

bors commented Aug 15, 2024

rust-timer commented Aug 15, 2024

Kobzol commented Aug 15, 2024

nnethercote commented Aug 15, 2024

khuey commented Aug 15, 2024

Rework MIR inlining debuginfo so function parameters show up in debuggers. #128861

Rework MIR inlining debuginfo so function parameters show up in debuggers. #128861

Conversation

khuey commented Aug 9, 2024 • edited by saethlin Loading

rustbot commented Aug 9, 2024

khuey commented Aug 9, 2024

rustbot commented Aug 9, 2024

khuey commented Aug 9, 2024

wesleywiser commented Aug 12, 2024

bors commented Aug 12, 2024

matthiaskrgr commented Aug 12, 2024

khuey commented Aug 12, 2024

khuey commented Aug 12, 2024

This comment has been minimized.

cjgillot commented Aug 12, 2024

saethlin commented Aug 12, 2024

rust-log-analyzer commented Aug 14, 2024

bors commented Aug 14, 2024

saethlin commented Aug 14, 2024

bors commented Aug 14, 2024

rust-log-analyzer commented Aug 15, 2024

bors commented Aug 15, 2024

khuey commented Aug 15, 2024

jieyouxu commented Aug 15, 2024

bors commented Aug 15, 2024

bors commented Aug 15, 2024

rust-timer commented Aug 15, 2024

Overall result: ❌✅ regressions and improvements - ACTION NEEDED

Instruction count

Max RSS (memory usage)

Cycles

Binary size

Kobzol commented Aug 15, 2024

nnethercote commented Aug 15, 2024

khuey commented Aug 15, 2024

khuey commented Aug 9, 2024 •

edited by saethlin

Loading