public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108795] New: [10/11/12/13 Regression] ICE in prep_operand, at cp/call.cc:6325
Date: Tue, 14 Feb 2023 19:41:26 +0000	[thread overview]
Message-ID: <bug-108795-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 108795
           Summary: [10/11/12/13 Regression] ICE in prep_operand, at
                    cp/call.cc:6325
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Started with r7 :


$ cat z1.cc
template <typename T> T g (T x)
{
  class C
  {
    __attribute__((transaction_safe)) ~C();
  };
  C::~C();
}
void f ()
{
  g (5);
}


$ gcc-13-20230212 -c z1.cc
z1.cc: In instantiation of 'T g(T) [with T = int]':
z1.cc:11:5:   required from here
z1.cc:7:6: internal compiler error: Segmentation fault
    7 |   C::~C();
      |   ~~~^~
0xeb71af crash_signal
        ../../gcc/toplev.cc:314
0x7b242d prep_operand
        ../../gcc/cp/call.cc:6325
0x7c8d67 build_new_op(op_location_t const&, tree_code, int, tree_node*,
tree_node*, tree_node*, tree_node*, tree_node**, int)
        ../../gcc/cp/call.cc:6956
0x985d3d build_x_unary_op(unsigned int, tree_code, cp_expr, tree_node*, int)
        ../../gcc/cp/typeck.cc:6820
0x9237fb tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:20496
0x924e34 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:20910
0x928e38 tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:19769
0x9279d1 tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:18758
0x927cce tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:18730
0x928678 tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:19110
0x92b970 tsubst_expr(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/cp/pt.cc:26707
0x92b970 instantiate_body
        ../../gcc/cp/pt.cc:26707
0x92c9df instantiate_decl(tree_node*, bool, bool)
        ../../gcc/cp/pt.cc:26997
0x9461db instantiate_pending_templates(int)
        ../../gcc/cp/pt.cc:27075
0x848f6a c_parse_final_cleanups()
        ../../gcc/cp/decl2.cc:4953
0x9f5be0 c_common_parse_file()
        ../../gcc/c-family/c-opts.cc:1266

             reply	other threads:[~2023-02-14 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 19:41 gscfq@t-online.de [this message]
2023-02-14 21:48 ` [Bug c++/108795] " mpolacek at gcc dot gnu.org
2023-02-23 15:20 ` [Bug c++/108795] [10/11/12/13 Regression] ICE in prep_operand, at cp/call.cc:6325 since r7-2549-gf3365c1201908df5 marxin at gcc dot gnu.org
2023-03-21 19:12 ` jason at gcc dot gnu.org
2023-03-22 16:05 ` cvs-commit at gcc dot gnu.org
2023-03-27 11:00 ` [Bug c++/108795] [10/11/12 " rguenth at gcc dot gnu.org
2023-04-21 20:48 ` cvs-commit at gcc dot gnu.org
2023-07-07 10:44 ` [Bug c++/108795] [11/12 " 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-108795-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).