https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100812
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2021-05-31
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
I recommend doing --save-temps --verbose and then running WPA without -quiet
flag. You'll see something like:
$ /home/marxin/bin/gcc/lib/gcc/x86_64-pc-linux-gnu/12.0.0/lto1 -dumpbase
./postgres.wpa -mtune=generic -march=x86-64 -O2 -O2 -O2 -Werror=vla
-Wimplicit-fallthrough=3 -Wformat-truncation=0 -Wno-stringop-truncation
-version -fno-openmp -fno-openacc -fno-pie -fcf-protection=none
-fno-strict-aliasing -fwrapv -fexcess-precision=standard
-fltrans-output-list=./postgres.ltrans.out -fwpa=16 -fresolution=postgres.res
-flinker-output=exec @./postgres.wpa.args.0
...
<devirt> {heap 66M} <cp> {heap 66M} <sra> {heap 66M} <cdtor> {heap 66M}
<fnsummary> {heap 66M} <inline> {GC released 3444k madv_dontneed 72k} {GC 143M
-> 128M} {heap 74M} <pure-const> {heap 74M} <modref> {heap 74M}
<free-fnsummary> {GC released 1024k madv_dontneed 14M} {GC trimmed to 123M,
139M mapped} {heap 74M} <static-var> {heap 74M} <single-use> {heap 74M}
<comdats> {heap 74M}
...
so one can identify the memory peak.
