diff options
| author | bors <bors@rust-lang.org> | 2024-04-26 11:16:05 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-04-26 11:16:05 +0000 |
| commit | 5ff8fbb2d83d423974d21d754b5ee56a4c869551 (patch) | |
| tree | 4cba6ab69ec4e1ddee7dfe96968679ee85f090fd /compiler/rustc_codegen_gcc | |
| parent | 6acb9e75ebc936df737381a9d0b7a7bccd6f0b2f (diff) | |
| parent | cd47a0ed086ca89faa64776ff15e118ba6aa27f3 (diff) | |
| download | rust-5ff8fbb2d83d423974d21d754b5ee56a4c869551.tar.gz rust-5ff8fbb2d83d423974d21d754b5ee56a4c869551.zip | |
Auto merge of #124393 - scottmcm:do-the-macros-still-matter, r=joboet
Convert some iter macros to normal functions With all the MIR optimization changes that have happened since these were written, let's see if they still actually matter. \*perf comes back\* Well, it looks like it's not longer relevant for instruction, cycle, nor wall-time perf. Looks like a bunch of things are maybe 10kb bigger in debug, but some are also 50k *smaller* in debug. So I think they should switch to being normal functions as the "greatly improves performance" justification for them being macros seems to no longer be true -- probably thanks to us always building `core` with `-Z inline-mir` so the difference is negligible.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions
