public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110699] [12/13/14 Regression] internal compiler error: tree check: expected array_type, have error_mark in array_ref_low_bound, at tree.cc:12754 Date: Fri, 21 Jul 2023 19:40:17 +0000 [thread overview] Message-ID: <bug-110699-4-2mhH9LjjXi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110699-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110699 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>: https://gcc.gnu.org/g:cfe53af09364d94fb86013f85ef598a1d47e0657 commit r14-2721-gcfe53af09364d94fb86013f85ef598a1d47e0657 Author: Roger Sayle <roger@nextmovesoftware.com> Date: Fri Jul 21 20:37:59 2023 +0100 PR c/110699: Defend against error_mark_node in gimplify.cc. This patch resolves PR c/110669, an ICE-after-error regression, by adding a check that the array type isn't error_mark_node in gimplify_compound_lval. 2023-07-21 Roger Sayle <roger@nextmovesoftware.com> Richard Biener <rguenther@suse.de> gcc/ChangeLog PR c/110699 * gimplify.cc (gimplify_compound_lval): If the array's type is error_mark_node then return GS_ERROR. gcc/testsuite/ChangeLog PR c/110699 * gcc.dg/pr110699.c: New test case.
next prev parent reply other threads:[~2023-07-21 19:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-17 9:14 [Bug c/110699] New: " 141242068 at smail dot nju.edu.cn 2023-07-17 14:24 ` [Bug c/110699] [12/13/14 Regression] " mpolacek at gcc dot gnu.org 2023-07-17 14:26 ` mpolacek at gcc dot gnu.org 2023-07-17 18:13 ` pinskia at gcc dot gnu.org 2023-07-21 19:40 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-23 12:49 ` roger at nextmovesoftware dot com 2023-07-23 17:55 ` 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-110699-4-2mhH9LjjXi@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).