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 c/99990] Crash in GCC-11/gimplify Date: Fri, 09 Apr 2021 12:18:16 +0000 [thread overview] Message-ID: <bug-99990-4-73pzEp8zut@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99990-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99990 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org CC| |jakub at gcc dot gnu.org Status|WAITING |ASSIGNED --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I can reproduce it. The problem seems to be that when handling the void *b[] = 0; error something overwrites TREE_TYPE (error_mark_node) to some other type.
next prev parent reply other threads:[~2021-04-09 12:18 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-09 11:33 [Bug c/99990] New: " k.even-mendoza at imperial dot ac.uk 2021-04-09 11:46 ` [Bug c/99990] " marxin at gcc dot gnu.org 2021-04-09 12:08 ` k.even-mendoza at imperial dot ac.uk 2021-04-09 12:18 ` jakub at gcc dot gnu.org [this message] 2021-04-09 12:32 ` [Bug c/99990] [8/9/10/11 Regression] ICE in gimplifier on invalid va_arg jakub at gcc dot gnu.org 2021-04-09 12:51 ` jakub at gcc dot gnu.org 2021-04-10 15:02 ` cvs-commit at gcc dot gnu.org 2021-04-10 15:03 ` [Bug c/99990] [8/9/10 " jakub at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:51 ` [Bug c/99990] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:52 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` jakub at gcc dot gnu.org 2022-01-03 20:54 ` 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-99990-4-73pzEp8zut@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).