public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christian.prochaska@genode-labs.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109804] New: internal compiler error in gimple-ssa-warn-access.cc
Date: Wed, 10 May 2023 20:55:47 +0000	[thread overview]
Message-ID: <bug-109804-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109804
           Summary: internal compiler error in gimple-ssa-warn-access.cc
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: christian.prochaska@genode-labs.com
  Target Milestone: ---

Created attachment 55042
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55042&action=edit
output from -freport-bug

during GIMPLE pass: waccess
test.cc: In function ‘T* Genode::construct_at(void*, ARGS&& ...) [with T = B;
ARGS = {C::C()::<unnamed enum>&}]’:
test.cc:37:19: internal compiler error: Segmentation fault
   37 | static inline T * Genode::construct_at(void *at, ARGS &&... args)
      |                   ^~~~~~
0xe67c7f crash_signal
        ../../gcc/toplev.cc:314
0xbb2320 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1626
0xbb23b9 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1724
0xbb23b9 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1724
0xbb23b9 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1724
0xbb23b9 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1724
0xbb23b9 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1724
0xbb23b9 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1724
0xbb7720 new_delete_mismatch_p
        ../../gcc/gimple-ssa-warn-access.cc:1763
0xbb7720 matching_alloc_calls_p
        ../../gcc/gimple-ssa-warn-access.cc:1786
0xbbf214 matching_alloc_calls_p
        ../../gcc/gimple-ssa-warn-access.cc:1984
0xbbf214 maybe_check_dealloc_call
        ../../gcc/gimple-ssa-warn-access.cc:3757
0xbbf214 check_call
        ../../gcc/gimple-ssa-warn-access.cc:4367
0xbbf214 check_block
        ../../gcc/gimple-ssa-warn-access.cc:4444
0xbbf214 execute
        ../../gcc/gimple-ssa-warn-access.cc:4766

             reply	other threads:[~2023-05-10 20:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 20:55 christian.prochaska@genode-labs.com [this message]
2023-05-10 20:56 ` [Bug c++/109804] " christian.prochaska@genode-labs.com
2023-05-10 20:59 ` [Bug tree-optimization/109804] [11/12/13/14 Regression] " mpolacek at gcc dot gnu.org
2023-05-10 21:02 ` mpolacek at gcc dot gnu.org
2023-05-10 21:13 ` [Bug tree-optimization/109804] " pinskia at gcc dot gnu.org
2023-05-10 21:13 ` pinskia at gcc dot gnu.org
2023-05-10 21:14 ` pinskia at gcc dot gnu.org
2023-05-10 21:16 ` [Bug tree-optimization/109804] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-05-10 21:17 ` pinskia at gcc dot gnu.org
2023-05-10 21:18 ` pinskia at gcc dot gnu.org
2023-05-10 21:48 ` mpolacek at gcc dot gnu.org
2023-05-11  6:30 ` rguenth at gcc dot gnu.org
2023-05-29 10:08 ` jakub at gcc dot gnu.org
2024-02-21  7:23 ` pinskia at gcc dot gnu.org
2024-02-22 17:29 ` cvs-commit at gcc dot gnu.org
2024-02-22 17:30 ` [Bug tree-optimization/109804] [11/12/13 " pinskia at gcc dot gnu.org
2024-02-22 21:13 ` cvs-commit at gcc dot gnu.org
2024-02-22 21:13 ` [Bug tree-optimization/109804] [11/12 " pinskia at gcc dot gnu.org
2024-05-08 17:11 ` cvs-commit at gcc dot gnu.org
2024-05-08 17:16 ` [Bug tree-optimization/109804] [11 " 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-109804-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).