public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbaptistapsilva at yahoo dot com.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99200] New: __PRETTY_FUNCTION__ used as template parameter causes internal compiler error (segmentation fault)
Date: Mon, 22 Feb 2021 14:28:37 +0000	[thread overview]
Message-ID: <bug-99200-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99200
           Summary: __PRETTY_FUNCTION__ used as template parameter causes
                    internal compiler error (segmentation fault)
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jbaptistapsilva at yahoo dot com.br
  Target Milestone: ---

Created attachment 50235
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50235&action=edit
Preprocessor output

Trying to use the macro __PRETTY_FUNCTION__ as a string-literal converted type
parameter (using the new feature of literal classes as non-type template
parameters, and using the technique applied here:
https://ctrpeach.io/posts/cpp20-string-literal-template-parameters/) causes a
segmentation fault on the compiler, which is then posted as an internal
compiler error.

The version, system type and configuration options are:
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
10.2.0-5ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-10
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-10-WJNXnb/gcc-10-10.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-WJNXnb/gcc-10-10.2.0/debian/tmp-gcn/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04)
Compiler executable checksum: d716f9df9d1b12ebc8fe860554136f35

The entire command line used was this:
g++-10 -std=c++2a -O3 pretty-function-segfault-gcc-10.cpp

The compiler output for the file is:
pretty-function-segfault-gcc-10.cpp: In function ‘consteval const char*
type_name()’:
pretty-function-segfault-gcc-10.cpp:37:49: internal compiler error:
Segmentation fault
   37 |     return TypeNameConverter<__PRETTY_FUNCTION__>{};
      |                                                 ^

             reply	other threads:[~2021-02-22 14:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 14:28 jbaptistapsilva at yahoo dot com.br [this message]
2021-02-22 14:34 ` [Bug c++/99200] " jbaptistapsilva at yahoo dot com.br
2021-02-22 15:24 ` mpolacek at gcc dot gnu.org
2021-02-22 15:32 ` jakub at gcc dot gnu.org
2021-02-22 17:09 ` jbaptistapsilva at yahoo dot com.br
2021-02-23 11:07 ` redi at gcc dot gnu.org
2021-03-03 21:11 ` mpolacek at gcc dot gnu.org
2021-04-24  4:15 ` cvs-commit at gcc dot gnu.org
2021-04-27 21:24 ` cvs-commit at gcc dot gnu.org
2021-05-01 18:46 ` ppalka 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-99200-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).