public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110106] [11/12/13/14 Regression] ICE on noexcept(noexcept(...)) with optional
Date: Sat, 03 Jun 2023 19:34:55 +0000	[thread overview]
Message-ID: <bug-110106-4-pxTjWaGFFU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110106-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The full backtrace of the seg fault:
t0.cc:3:36: internal compiler error: Segmentation fault
    3 | void y(j<0> z) noexcept(noexcept(g{z}));
      |                                    ^
0x128f4af crash_signal
        /home/apinski/src/upstream-gcc-git/gcc/gcc/toplev.cc:314
0x7f37b9c54def ???
       
/usr/src/debug/glibc-2.34-60.el9.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0xa40753 tree_check(tree_node*, char const*, int, char const*, tree_code)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/tree.h:3539
0xa40753 is_really_empty_class(tree_node*, bool)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/class.cc:8960
0xa6aa99 potential_constant_expression_1
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:9095
0xa69714 potential_constant_expression_1
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:9309
0xa6be0c potential_constant_expression_1(tree_node*, bool, bool, bool, bool,
int)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:10131
0xa6be0c is_rvalue_constant_expression(tree_node*)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:10215
0xba4e75 cp_parser_constant_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:10801
0xba6301 cp_parser_initializer_clause
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:25522
0xba58e1 cp_parser_initializer_list
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:25812
0xba58e1 cp_parser_braced_list
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:25563
0xba8b4c cp_parser_functional_cast
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:32647
0xbb8547 cp_parser_postfix_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:7703
0xba0d6b cp_parser_binary_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:10147
0xba1c72 cp_parser_assignment_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:10491
0xba41c3 cp_parser_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:10661
0xbd6aa8 cp_parser_unary_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:8937
0xba0d6b cp_parser_binary_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:10147
0xba1c72 cp_parser_assignment_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/parser.cc:10491
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

  parent reply	other threads:[~2023-06-03 19:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 18:18 [Bug c++/110106] New: " stevenxia990430 at gmail dot com
2023-06-03 18:29 ` [Bug c++/110106] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-06-03 19:31 ` pinskia at gcc dot gnu.org
2023-06-03 19:34 ` pinskia at gcc dot gnu.org [this message]
2023-06-05  6:46 ` rguenth at gcc dot gnu.org
2023-06-05 15:28 ` mpolacek at gcc dot gnu.org
2023-07-18 20:01 ` mpolacek at gcc dot gnu.org
2023-07-21 17:52 ` cvs-commit at gcc dot gnu.org
2023-12-12  0:37 ` [Bug c++/110106] [11/12/13 " cvs-commit at gcc dot gnu.org
2023-12-12  0:38 ` [Bug c++/110106] [11/12 " mpolacek 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-110106-4-pxTjWaGFFU@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).