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

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Slightly reduced:

template <int N>
struct A
{
  constexpr A (const char (&s)[N]) { for (int i = 0; i < N; i++) v[i] = s[i];
v[N] = 0; }
  char v[N + 1];
};

template <A s>
struct B
{
  constexpr operator const char *() { return s.v; }
};

template <typename T>
const char *
foo ()
{ 
  return B<__PRETTY_FUNCTION__>{};
}

template <typename T>
const char *
bar ()
{ 
  return B<__FUNCTION__>{};
}

int
main ()
{
  auto a = foo <int> ();
  auto b = bar <double> ();
}

  parent reply	other threads:[~2021-02-22 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 14:28 [Bug c++/99200] New: " jbaptistapsilva at yahoo dot com.br
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 [this message]
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-LkdX5P5W23@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).