https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26854
--- Comment #149 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Richard Biener from comment #148) > (In reply to lucier from comment #145) > > Created attachment 54424 [details] > > CPU and Memory usage reports for mainline 13.0.1 (mainline) > > > > Thank you for looking at this issue again. > > > > I built today's mainline and ran three tests: > > > > /pkgs/gcc-mainline/bin/gcc -v -c -O2 -fmem-report -ftime-report compiler.i > > -save-temps >& report-compiler4 > > /pkgs/gcc-mainline/bin/gcc -v -c -O2 -fmem-report -ftime-report all.i > > -save-temps >& report-all4 > > /pkgs/gcc-mainline/bin/gcc -v -c -O2 -fmem-report -ftime-report _num.i > > -save-temps >& report-_num4 > > > > The reports are collected here. Compiling compiler.i required over 30GB at > > certain points. I haven't really studied these types of reports in a while, > > so I can offer little analysis. > > Yes, I've mostly looked at performance with -O1 since that's what we suggest > if -O2+ run into issues. That seems to be in check with GCC 13, memory > peak is at ~1GB for me for compiler.i > > I'll look at -O2 now, the mdreorg thing seems "new" (DF RD is a known source > of issues here ...). So with -O2 -mno-stv we have df reaching defs : 18.54 ( 9%) df use-def / def-use chains : 10.37 ( 5%) parser function body : 20.29 ( 10%) tree VRP : 17.82 ( 9%) tree PTA : 45.85 ( 23%) TOTAL : 202.90 and a peak memory use of still 26GB.
