public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andris.pavenis at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/97240] New: Analyzer runs out of memory building C++ source
Date: Tue, 29 Sep 2020 11:11:08 +0000	[thread overview]
Message-ID: <bug-97240-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 97240
           Summary: Analyzer runs out of memory building C++ source
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: andris.pavenis at iki dot fi
  Target Milestone: ---

Created attachment 49285
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49285&action=edit
Preprocessed source

Compiling source with -fanalyzer incommand line causes gcc-10.2.0 run out of
memory.

g++ -c -v -std=c++17 -fanalyzer FastMathTest.ii 
Using built-in specs.
COLLECT_GCC=g++
Kohde: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --with-isl
--with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit
--enable-cet=auto --enable-checking=release --enable-clocale=gnu
--enable-default-pie --enable-default-ssp --enable-gnu-indirect-function
--enable-gnu-unique-object --enable-install-libiberty --enable-linker-build-id
--enable-lto --enable-multilib --enable-plugin --enable-shared
--enable-threads=posix --disable-libssp --disable-libstdcxx-pch
--disable-libunwind-exceptions --disable-werror
gdc_include_dir=/usr/include/dlang/gdc
Säiemalli: posix
Supported LTO compression algorithms: zlib zstd
gcc-versio 10.2.0 (GCC) 
COLLECT_GCC_OPTIONS='-c' '-v' '-std=c++17' '-fanalyzer' '-shared-libgcc'
'-mtune=generic' '-march=x86-64'
 /usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/cc1plus -fpreprocessed FastMathTest.ii
-quiet -dumpbase FastMathTest.ii -mtune=generic -march=x86-64 -auxbase
FastMathTest -std=c++17 -version -fanalyzer -o /tmp/ccZO5KJm.s
GNU C++17 (GCC) versio 10.2.0 (x86_64-pc-linux-gnu)
        käännetty GNU C:n versiolla 10.2.0, GMP version 6.2.0, MPFR version
4.1.0, MPC version 1.1.0, isl version isl-0.21-GMP

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C++17 (GCC) versio 10.2.0 (x86_64-pc-linux-gnu)
        käännetty GNU C:n versiolla 10.2.0, GMP version 6.2.0, MPFR version
4.1.0, MPC version 1.1.0, isl version isl-0.21-GMP

GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 2affcd71b0797e2421aae734ab600c81


Killed compile when memory use exceeded 70 GB.

             reply	other threads:[~2020-09-29 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 11:11 andris.pavenis at iki dot fi [this message]
2022-02-15 18:31 ` [Bug analyzer/97240] " andris at gcc dot gnu.org
2022-02-16  9:49 ` andris at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-97240-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).