https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
palmer at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palmer at gcc dot gnu.org,
| |vineetg at gcc dot gnu.org
--- Comment #7 from palmer at gcc dot gnu.org ---
(In reply to Andreas Schwab from comment #3)
> Here are the build times of the stage1 compiler:
>
> 20230714 21573
> 20230722 19932 -7.6%
> 20230728 21608 +8.4%
> 20230804 21841 +1.0%
> 20230811 25016 +14.5%
> 20230818 25429 +1.7%
> 20230825 25872 +1.7%
> 20230901 25965 +0.4%
> 20230908 28824 +11.0%
> 20230915 30926 +7.3%
> 20230922 40180 +30.0%
Did anything else change? The latest binutils has better debug support, so I
could imagine us ending up with some longer compiler times as a result -- there
has to be more than just that here, though.
Aside from that we have had a ton of vector codegen go in over the last few
months, but this is a pretty huge increase so I agree it's worrisome. I'm
adding Vineet to the CC list, as he's been doing some SPEC runs. I don't think
we've had any major runtime regressions, but looks like dwarf2out.cc times have
crept up a bit which is also worrisome.
Also what exactly are you timing? Native boostraps on QEMU?
