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/95580] [11 Regression] ICE in tree_strip_any_location_wrapper at gcc/tree.h:4011 since r11-959-gb825a22890740f34 Date: Sun, 14 Jun 2020 10:07:41 +0000 [thread overview] Message-ID: <bug-95580-4-PIqpUnqwU1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95580-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95580 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:b2229175b53e3b1c58b4aa963e3d0bb06ca063bf commit r10-8297-gb2229175b53e3b1c58b4aa963e3d0bb06ca063bf Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Jun 9 08:39:36 2020 +0200 c-family: Fix up MEM_REF printing [PR95580] The C FE in the MEM_REF printing ICEs if the type of the first argument (which due to useless pointer conversions can be an arbitrary type) is a pointer to an incomplete type. The code just wants to avoid printing a cast if it is a pointer to single byte elements. 2020-06-09 Jakub Jelinek <jakub@redhat.com> PR c/95580 * c-pretty-print.c (c_pretty_printer::unary_expression): Handle the case when MEM_REF's first argument has type pointer to incomplete type. * gcc.dg/pr95580.c: New test. (cherry picked from commit d6dbb71e468d0db561cc9eca99eeaca1efb81c11)
prev parent reply other threads:[~2020-06-14 10:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 15:23 [Bug tree-optimization/95580] New: " marxin at gcc dot gnu.org 2020-06-08 15:23 ` [Bug tree-optimization/95580] " marxin at gcc dot gnu.org 2020-06-08 17:25 ` [Bug c/95580] " jakub at gcc dot gnu.org 2020-06-08 17:31 ` jakub at gcc dot gnu.org 2020-06-09 6:40 ` cvs-commit at gcc dot gnu.org 2020-06-09 6:40 ` jakub at gcc dot gnu.org 2020-06-14 10:07 ` cvs-commit at gcc dot gnu.org [this message]
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-95580-4-PIqpUnqwU1@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).