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/105635] [12 Regression] ICE in gimple_parm_array_size, at pointer-query.cc:592 since r12-6606-g9d6a0f388eb048f8 Date: Mon, 30 May 2022 03:36:44 +0000 [thread overview] Message-ID: <bug-105635-4-OMPD407iyB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105635-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105635 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7b88f9b8881b7653b5a834da1b2b8fda463e61c0 commit r12-8432-g7b88f9b8881b7653b5a834da1b2b8fda463e61c0 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu May 19 11:56:21 2022 +0200 pointer-query: Fix ICE with non-pointer param [PR105635] The gimple_parm_array_size function comment talks about pointe parameters but doesn't actually verify it, it checks whether an attribute is present on the function and then just uses TREE_TYPE (TREE_TYPE (var)) which assumes a pointer type (or in theory could work for ARRAY_TYPE but c-family languages which only have that attribute will never have ARRAY_TYPE parameters; and for VECTOR_TYPE/COMPLEX_TYPE it would mean something quite different). So, this patch punts early if var doesn't have pointer/reference type. 2022-05-19 Jakub Jelinek <jakub@redhat.com> PR c/105635 * pointer-query.cc (gimple_parm_array_size): Return NULL if var doesn't have pointer or reference type. * gcc.dg/pr105635.c: New test. (cherry picked from commit 3b4daa0b3c3d8eb2ac3b40ad6898f314ed4d7919)
next prev parent reply other threads:[~2022-05-30 3:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-17 18:48 [Bug c/105635] New: [12/13 Regression] ICE in gimple_parm_array_size, at pointer-query.cc:592 gscfq@t-online.de 2022-05-18 7:37 ` [Bug c/105635] [12/13 Regression] ICE in gimple_parm_array_size, at pointer-query.cc:592 since r12-6606-g9d6a0f388eb048f8 marxin at gcc dot gnu.org 2022-05-18 10:31 ` jakub at gcc dot gnu.org 2022-05-18 12:39 ` rguenth at gcc dot gnu.org 2022-05-19 9:57 ` cvs-commit at gcc dot gnu.org 2022-05-19 9:59 ` [Bug c/105635] [12 " jakub at gcc dot gnu.org 2022-05-30 3:36 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-30 7:57 ` jakub 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-105635-4-OMPD407iyB@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).