public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113397] [14 Regression] ICE: SIGSEGV in tree_check (tree.h:3611) with -fdump-ada-spec-slim on gcc.c-torture/execute/pr22061-2.c Date: Mon, 15 Jan 2024 15:49:36 +0000 [thread overview] Message-ID: <bug-113397-4-Sm04KlG7zU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113397-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113397 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ebotcazou at gcc dot gnu.org, | |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r14-1143-g42d1612eb5c3b2ee327bc3336bfcbc43a0d0fc5b but I'd say check_type_name_conflict expectations are just wrong, even when a type has a TYPE_NAME which is a TYPE_DECL, it doesn't imply it has a DECL_NAME, in this case the TYPE_DECL has been created just to make the gimplifier happy.
next prev parent reply other threads:[~2024-01-15 15:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 12:00 [Bug tree-optimization/113397] New: " zsojka at seznam dot cz 2024-01-15 12:03 ` [Bug tree-optimization/113397] " zsojka at seznam dot cz 2024-01-15 12:39 ` rguenth at gcc dot gnu.org 2024-01-15 15:49 ` jakub at gcc dot gnu.org [this message] 2024-01-15 16:31 ` [Bug ada/113397] " ebotcazou at gcc dot gnu.org 2024-01-16 11:17 ` cvs-commit at gcc dot gnu.org 2024-01-16 11:18 ` ebotcazou 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-113397-4-Sm04KlG7zU@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).