Repository navigation
Outline constant messages from panicking macros - #163766
Conversation
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[EXPERIMENT] Outline some panics with constant messages
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (caa37fb): comparison URL. Overall result: ❌✅ regressions and improvements - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 1.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 0.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.2%, secondary -0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 490.122s -> 490.205s (0.02%) |
|
btw. I was wondering whether we should maybe do this automatically. Either change the panic macros to output a argument-less function definition and a call, or do the equivalent in some mir opt. [edit] oh.. lol, that's what you did 😆 I should have looked at the code before commenting |
1b49c26 to
ac8f493
Compare
|
rustbot has assigned @Mark-Simulacrum. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Outline constant messages from panicking macros
This comment has been minimized.
This comment has been minimized.
ac8f493 to
61ca6bb
Compare
This comment has been minimized.
This comment has been minimized.
|
That can’t be right… |
|
Yes, this looks like #t-compiler/performance > Suspiciously positive results (noise in get_module_children) again |
|
r? ChrisDenton This seems quite marginal? |
|
I think we should re-measure this to get real results. It seems that this benchmark noise got stable in last few days. @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Outline constant messages from panicking macros
|
I’d expect the same results as on the first run (before I polished the code and extended it to |
This comment has been minimized.
This comment has been minimized.
Fair enough. r=me unless the new perf results are somehow bad (though tbh in that case I'd suspecting something went wrong). |
|
Finished benchmarking commit (fe83376): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.9%, secondary 1.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -0.4%, secondary 1.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary -1.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 487.9s -> 486.879s (-0.21%) |
|
@bors r+ |
|
@bors rollup=iffy |
…uwer Rollup of 5 pull requests Successful merges: - #163766 (Outline constant messages from panicking macros) - #147368 (Add extra `unchecked_disjoint_bitor` implementations.) - #164748 (Use 64-bit futex syscalls on RV32 Linux) - #164520 (powerpc: implement c-variadic correctly for softfloat targets) - #164671 (add maintainers for tier 2 riscv64 targets (baremetal only))
…uwer Rollup of 5 pull requests Successful merges: - rust-lang/rust#163766 (Outline constant messages from panicking macros) - rust-lang/rust#147368 (Add extra `unchecked_disjoint_bitor` implementations.) - rust-lang/rust#164748 (Use 64-bit futex syscalls on RV32 Linux) - rust-lang/rust#164520 (powerpc: implement c-variadic correctly for softfloat targets) - rust-lang/rust#164671 (add maintainers for tier 2 riscv64 targets (baremetal only))
View all comments
This emits (very slightly) less code per call site because it's passing one less argument (the implicit caller location is still passed).
Inspired by #163657