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++/112437] ICE with throw inside concept sometimes and -std=c++20
Date: Wed, 08 Nov 2023 05:29:13 +0000	[thread overview]
Message-ID: <bug-112437-4-RfAgzdeSzz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112437-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The backtrace:
```
t55.cc:4:37: internal compiler error: Segmentation fault
    4 | concept Throwable = requires(T x) { throw x; };
      |                                     ^~~~~~~
0x133b01f crash_signal
        /home/apinski/src/upstream-gcc-git/gcc/gcc/toplev.cc:316
0x7f18dce54def ???
       
/usr/src/debug/glibc-2.34-60.el9.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0xcf7fa2 treat_lvalue_as_rvalue_p(tree_node*, bool)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/typeck.cc:10732
0xb5d62f build_throw(unsigned int, tree_node*)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/except.cc:723
0xc70ede tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/pt.cc:20944
0xac70d3 tsubst_valid_expression_requirement
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:1990
0xace475 tsubst_simple_requirement
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:2024
0xace475 tsubst_requirement
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:2221
0xace475 tsubst_requires_expr
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:2351
0xacea6a tsubst_requires_expr(tree_node*, tree_node*, int, tree_node*)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:2370
0xc6fad5 tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/pt.cc:21472
0xacfc1e satisfy_atom
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:3036
0xacfc1e satisfy_constraint_r
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:3101
0xad0202 satisfy_normalized_constraints
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:3126
0xacd3ce satisfy_nondeclaration_constraints
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:3208
0xacd3ce constraint_satisfaction_value
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:3373
0xad02e6 evaluate_concept_check(tree_node*)
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constraint.cc:3421
0xab2f60 cxx_eval_constant_expression
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:8346
0xabc7d9 cxx_eval_outermost_constant_expr
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:8670
0xac2612 maybe_constant_init_1
        /home/apinski/src/upstream-gcc-git/gcc/gcc/cp/constexpr.cc:9181
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-11-08  5:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  5:22 [Bug c++/112437] New: " pinskia at gcc dot gnu.org
2023-11-08  5:28 ` [Bug c++/112437] " pinskia at gcc dot gnu.org
2023-11-08  5:29 ` pinskia at gcc dot gnu.org [this message]
2023-11-08 12:00 ` redi at gcc dot gnu.org
2024-01-24  3:08 ` mpolacek at gcc dot gnu.org
2024-02-01 14:00 ` cvs-commit at gcc dot gnu.org
2024-02-01 15:41 ` cvs-commit at gcc dot gnu.org
2024-02-01 15:50 ` cvs-commit at gcc dot gnu.org
2024-02-01 15:56 ` 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-112437-4-RfAgzdeSzz@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).