public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112878] ICE: in ctf_add_slice, at ctfc.cc:499 with -std=c23 -gctf1
Date: Fri, 19 Jan 2024 15:57:35 +0000	[thread overview]
Message-ID: <bug-112878-4-BiaOLbF30o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112878-4@http.gcc.gnu.org/bugzilla/>

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

Zdenek Sojka <zsojka at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |zsojka at seznam dot cz

--- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> ---
Also fails with a union:
$ cat testcase.c 
union {
  _BitInt(448) f2 : 1;
} b;
$ x86_64-pc-linux-gnu-gcc -gbtf testcase.c 
testcase.c:3:1: internal compiler error: in ctf_add_slice, at ctfc.cc:499
    3 | } b;
      | ^
0xd60e19 ctf_add_slice(ctf_container*, unsigned int, unsigned long, unsigned
int, unsigned int, die_struct*)
        /repo/gcc-trunk/gcc/ctfc.cc:499
0x101d9d0 gen_ctf_sou_type
        /repo/gcc-trunk/gcc/dwarf2ctf.cc:617
0x101d177 gen_ctf_type
        /repo/gcc-trunk/gcc/dwarf2ctf.cc:892
...

  reply	other threads:[~2024-01-19 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 10:51 [Bug debug/112878] New: " iamanonymous.cs at gmail dot com
2024-01-19 15:57 ` zsojka at seznam dot cz [this message]
2024-01-20  9:02 ` [Bug debug/112878] " pinskia at gcc dot gnu.org
2024-04-09 18:34 ` [Bug debug/112878] ICE: in ctf_add_slice, at ctfc.cc:499 with _BitInt > 255 in a struct and -gctf1 ibhagat at gcc dot gnu.org
2024-04-09 18:44 ` pinskia at gcc dot gnu.org
2024-04-09 21:18 ` ibhagat at gcc dot gnu.org
2024-04-11  0:32 ` cvs-commit 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-112878-4-BiaOLbF30o@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).