[Bug analyzer/95031] New: GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

[Bug analyzer/95031] New: GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

[noloader at gmail dot com]

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

            Bug ID: 95031
           Summary: GCC 10 Analyzer and fatal error: Terminated signal
                    terminated program cc1plus
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: noloader at gmail dot com
  Target Milestone: ---

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

Hi Everyone,

I'm trying out the analyzer on a C++ project. I'm working on Fedora 32 with GCC
10.

  $ gcc --version
  gcc (GCC) 10.0.1 20200430 (Red Hat 10.0.1-0.14)

Here's what I am seeing:

  g++ -fPIC -pthread -pipe -DNDEBUG -g2 -O3 -fanalyzer -c dll.cpp
  g++: fatal error: Terminated signal terminated program cc1plus
  compilation terminated.
  make: *** [GNUmakefile:1693: dll.o] Error 1

It is fairly easy to duplicate with live code. Unfortunately, I am not sure
what is needed for a reproducer based on the error message. It can be
duplicated with live code using:

  $ git clone https://github.com/weidai11/cryptopp.git
  $ cd cryptopp
  $ CXXFLAGS="-DNDEBUG -g2 -O3 -fanalyzer" make dll.o
  ...
  g++: fatal error: Terminated signal terminated program cc1plus
  compilation terminated.

Attached is the output with a -save-temps. If someone would kindly provide
instructions, then I would be happy to troubleshot it further.

The file dll.cpp is a real bastard. It includes a lot of template classes. Its
sole purpose is to instantiate a bunch of template classes so the object file
has concrete objects in it. I would not be surprised if some sort of resource
exhaustion was occurring.

[Bug analyzer/95031] GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

[marxin at gcc dot gnu.org]

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-05-11
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1
                 CC|                            |marxin at gcc dot gnu.org

[Bug analyzer/95031] GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

[marxin at gcc dot gnu.org]

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

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
It finished for me with ~16GB memory eaten in:
user    3m59.520s

[Bug analyzer/95031] GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

[dmalcolm at gcc dot gnu.org]

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

--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Please note that C++ isn't supported in the -fanalyzer implementation in GCC
10.  I hope to get it working for GCC 11 (but there's a lot of work to do).

[Bug analyzer/95031] GCC 10 Analyzer and fatal error: Terminated signal terminated program cc1plus

[noloader at gmail dot com]

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

--- Comment #3 from Jeffrey Walton <noloader at gmail dot com> ---
(In reply to David Malcolm from comment #2)
> Please note that C++ isn't supported in the -fanalyzer implementation in GCC
> 10.  I hope to get it working for GCC 11 (but there's a lot of work to do).

Oh, sorry about that. That explains a lot.

You might want to add that information to
https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10/. Maybe
even add an example of the unexpected beahvior when using C++. I started the
Analyzer testing after reading the blog.