[Bug target/98746] New: [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[Bug target/98746] New: [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[doko at debian dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

            Bug ID: 98746
           Summary: [11 Regression] memory hog for a lto+pgo build on
                    powerpc64*-linux-gnu
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: doko at debian dot org
  Target Milestone: ---

seen with the trunk. A native combined profiled & lto build takes a bit more
than 16GB of memory with -j16, and just under 8GB with -j4 and link
serialization set to 1.  I don't see this on other 64bit builds.

marking as a regression, a make -j4 build with 8GB of memory does succeed with
GCC 10.

attaching memory usage reports for ppc64el -j16 and -j4, plus a comparison for
x86_64.

[Bug target/98746] [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[doko at debian dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

--- Comment #1 from Matthias Klose <doko at debian dot org> ---
the reports are too big, please find them at
https://people.debian.org/~doko/tmp/  usage-*

eog isn't able to disaply those, I used gwenview to display the svg files.

[Bug target/98746] [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[doko at debian dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

--- Comment #2 from Matthias Klose <doko at debian dot org> ---
the -j4 build is configured with

         --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++
         --prefix=/usr/lib/gcc-snapshot
         --with-gcc-major-version-only
         --program-prefix=
         --enable-shared
         --enable-linker-build-id
         --disable-nls
         --enable-bootstrap
         --enable-clocale=gnu
         --enable-libstdcxx-debug
         --enable-libstdcxx-time=yes
         --with-default-libstdcxx-abi=new
         --enable-gnu-unique-object
         --enable-plugin
         --with-system-zlib
         --enable-libphobos-checking=release
         --with-target-system-zlib=auto
         --enable-objc-gc=auto
         --enable-secureplt
         --with-cpu=power8
         --enable-targets=powerpcle-linux
         --disable-multilib
         --enable-multiarch
         --disable-werror
         --with-long-double-128
        
--enable-offload-targets=nvptx-none=/<<PKGBUILDDIR>>/debian/tmp-nvptx/usr/lib/gcc-snapshot
         --without-cuda-driver
         --enable-checking=yes,extra,rtl
         --build=powerpc64le-linux-gnu
         --host=powerpc64le-linux-gnu
         --target=powerpc64le-linux-gnu
         --with-build-config=bootstrap-lto-lean
         --enable-link-serialization=1

and built with

make -j4 profiledbootstrap-lean

[Bug target/98746] [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |11.0

[Bug target/98746] [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2021-02-23

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Did the situation improve with the recent memory usage improvements?

[Bug target/98746] [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[doko at debian dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

--- Comment #4 from Matthias Klose <doko at debian dot org> ---
trunk 20210220 with 8441545d4f2afb9e9342e0dac378eafd03f00462 reverted uses less
than 100MB for the compilation.

[Bug target/98746] [11 Regression] memory hog for a lto+pgo build on powerpc64*-linux-gnu

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98746

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
So fixed.