public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105809] New: GCC ICE when deal with __PRETTY_FUNCTION__ inside macro
Date: Wed, 01 Jun 2022 21:18:54 +0000	[thread overview]
Message-ID: <bug-105809-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105809
           Summary: GCC ICE when deal with __PRETTY_FUNCTION__ inside
                    macro
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: unlvsur at live dot com
  Target Milestone: ---

GCC ICE:
https://godbolt.org/z/Gfzov4j3b
clang:
https://godbolt.org/z/ebdPPK77r

             reply	other threads:[~2022-06-01 21:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 21:18 unlvsur at live dot com [this message]
2022-06-01 21:23 ` [Bug c++/105809] " pinskia at gcc dot gnu.org
2022-06-01 21:32 ` [Bug c++/105809] [10/11/12/13 Regression] " mpolacek at gcc dot gnu.org
2022-06-01 21:35 ` pinskia at gcc dot gnu.org
2022-06-01 21:38 ` pinskia at gcc dot gnu.org
2022-06-28 10:49 ` [Bug c++/105809] [10/11/12/13 Regression] __PRETTY_FUNCTION__ in constexpr in function vs NSDMI jakub at gcc dot gnu.org
2022-10-19 10:16 ` rguenth at gcc dot gnu.org
2023-03-16 19:19 ` jason at gcc dot gnu.org
2023-03-16 22:12 ` cvs-commit at gcc dot gnu.org
2023-04-18 20:46 ` [Bug c++/105809] [10/11/12 " cvs-commit at gcc dot gnu.org
2023-07-07 10:43 ` [Bug c++/105809] [11 " rguenth 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-105809-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).