public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tocic at protonmail dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109730] New: ICE in c_common_parse_file()
Date: Thu, 04 May 2023 09:20:01 +0000	[thread overview]
Message-ID: <bug-109730-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109730
           Summary: ICE in c_common_parse_file()
           Product: gcc
           Version: 13.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tocic at protonmail dot ch
  Target Milestone: ---

Created attachment 54991
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54991&action=edit
result of -freport-bug

I'm trying to compile https://github.com/cschreib/snitch. `gcc 12.2.1` works
fine, `gcc 13.1.1` produces an ICE on the line

```
std::array<ElemType, MaxLength> data_buffer = {};
```

Originally posted here https://bugs.archlinux.org/task/78385.

             reply	other threads:[~2023-05-04  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  9:20 tocic at protonmail dot ch [this message]
2023-05-04 10:22 ` [Bug c++/109730] [12/13/14 regression] ICE in contains_struct_check sjames at gcc dot gnu.org
2023-05-04 11:39 ` rguenth at gcc dot gnu.org
2023-05-04 11:52 ` sjames at gcc dot gnu.org
2023-05-04 12:18 ` [Bug c++/109730] [12/13/14 regression] ICE in contains_struct_check since r12-9441-g94569d91bd4c60 sjames at gcc dot gnu.org
2023-05-04 20:04 ` 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-109730-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).