public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tim at klingt dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105725] New: [ICE] segfault with `-Wmismatched-tags`
Date: Wed, 25 May 2022 03:46:14 +0000	[thread overview]
Message-ID: <bug-105725-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105725
           Summary: [ICE] segfault with `-Wmismatched-tags`
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tim at klingt dot org
  Target Milestone: ---

possibly a duplicate of 103703, but the backtrace is slightly different, so i'd
file a separate ticket for it:

cwise gave me:
```
template <class T> class T::QPrivateSignal
```

stack trace
```
0xd8e7d3 crash_signal
        ../../src/gcc/toplev.cc:322
0x7f59c77a051f ???
        ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7ba59e class_decl_loc_t::add(cp_parser*, unsigned int, tag_types, tree_node*,
bool, bool)
        ../../src/gcc/cp/parser.cc:33489
0x7e44ba cp_parser_elaborated_type_specifier
        ../../src/gcc/cp/parser.cc:20659
0x7c8972 cp_parser_type_specifier
        ../../src/gcc/cp/parser.cc:19370
0x7d8e90 cp_parser_type_specifier_seq
        ../../src/gcc/cp/parser.cc:24349
0x7d7214 cp_parser_type_id_1
        ../../src/gcc/cp/parser.cc:24149
0x7d9fb3 cp_parser_template_type_arg
        ../../src/gcc/cp/parser.cc:24257
0x7da119 cp_parser_template_argument
        ../../src/gcc/cp/parser.cc:18799
0x7da119 cp_parser_template_argument_list
        ../../src/gcc/cp/parser.cc:18723
0x7da119 cp_parser_enclosed_template_argument_list
        ../../src/gcc/cp/parser.cc:32029
0x7db50f cp_parser_template_id
        ../../src/gcc/cp/parser.cc:18262
0x7dbcc9 cp_parser_class_name
        ../../src/gcc/cp/parser.cc:25698
0x7d386e cp_parser_qualifying_entity
        ../../src/gcc/cp/parser.cc:7116
0x7d386e cp_parser_nested_name_specifier_opt
        ../../src/gcc/cp/parser.cc:6798
0x7eaa4c cp_parser_simple_type_specifier
        ../../src/gcc/cp/parser.cc:19761
0x7c89d5 cp_parser_type_specifier
        ../../src/gcc/cp/parser.cc:19420
0x7d8e90 cp_parser_type_specifier_seq
        ../../src/gcc/cp/parser.cc:24349
0x7d7214 cp_parser_type_id_1
        ../../src/gcc/cp/parser.cc:24149
0x7d9fb3 cp_parser_template_type_arg
        ../../src/gcc/cp/parser.cc:24257
```

             reply	other threads:[~2022-05-25  3:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  3:46 tim at klingt dot org [this message]
2022-05-25  8:38 ` [Bug c++/105725] " tim at klingt dot org
2022-05-25 11:25 ` mpolacek at gcc dot gnu.org
2022-05-27 14:25 ` mpolacek at gcc dot gnu.org
2022-05-27 16:03 ` cvs-commit at gcc dot gnu.org
2022-05-27 16:08 ` cvs-commit at gcc dot gnu.org
2022-05-27 16:09 ` mpolacek at gcc dot gnu.org
2022-10-24  8:50 ` cvs-commit at gcc dot gnu.org
2022-10-24  8:51 ` rguenth at gcc dot gnu.org
2022-10-25 22:34 ` pinskia 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-105725-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).