public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/113480] New: avr: internal compiler error: in add_dwarf_attr, at dwarf2out.cc:4503 Date: Thu, 18 Jan 2024 13:35:02 +0000 [thread overview] Message-ID: <bug-113480-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113480 Bug ID: 113480 Summary: avr: internal compiler error: in add_dwarf_attr, at dwarf2out.cc:4503 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: gjl at gcc dot gnu.org Target Milestone: --- This is a relatively new ICE that I see on the avr target. Compliled with "version 14.0.1 20240118 (experimental) (avr)" $ avr-gcc pr83801.c -g -O3 -std=gnu99 -mmcu=atmega128 /* { dg-options { "-std=gnu99" } } */ /* { dg-do run { target { ! avr_tiny } } } */ __attribute((noinline,noclone)) char to_ascii (unsigned i) { static const char __flash code_tab[] = "0123456789"; return code_tab[i]; } int main() { if (to_ascii (2) != '2') __builtin_abort(); return 0; } I am not sure if it's related to address-spaces, but there are fails that don't have ASes like gcc.target/avr/torture/pr109907-2.c (but that has __int24 though). Target: avr Configured with: ../../source/gcc-master/configure --target=avr --disable-nls --with-dwarf2 --with-gnu-as --with-gnu-ld --disable-shared --with-fixed-point=no --with-long-double=64 --enable-languages=c,c++ Thread model: single Supported LTO compression algorithms: zlib gcc version 14.0.1 20240118 (experimental) (GCC)
next reply other threads:[~2024-01-18 13:35 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 13:35 gjl at gcc dot gnu.org [this message] 2024-01-18 13:41 ` [Bug debug/113480] [14 Regression] " gjl at gcc dot gnu.org 2024-01-18 13:45 ` rguenth at gcc dot gnu.org 2024-01-18 13:56 ` gjl at gcc dot gnu.org 2024-01-18 14:23 ` [Bug debug/113480] " rguenth at gcc dot gnu.org 2024-01-18 14:47 ` pinskia at gcc dot gnu.org 2024-01-18 17:57 ` 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-113480-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: linkBe 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).