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/105660] [12 Regression] ICE in warn_parm_array_mismatch when merging two function decls and VLA arguments since r12-1218-gc6503fa93b5565c9 Date: Tue, 09 May 2023 06:42:35 +0000 [thread overview] Message-ID: <bug-105660-4-0AcgjHyNws@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105660-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105660 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Martin Uecker <uecker@gcc.gnu.org>: https://gcc.gnu.org/g:a4308f9d432a108026d6ae8ad99d40a52eea341f commit r12-9522-ga4308f9d432a108026d6ae8ad99d40a52eea341f Author: Martin Uecker <uecker@tugraz.at> Date: Wed Feb 8 15:02:43 2023 +0100 Fix ICE related to implicit access attributes for VLA arguments [PR105660] When constructing the specifier string when merging an access attribute that encodes information about VLA arguments, the string was constructed in random order by iterating through a hash table. Fix this by iterating though the list of arguments. gcc/c-family/Changelog: PR c/105660 * c-attribs.cc (append_access_attr): Use order of arguments when construction string. (append_access_attr_idxs): Rename and make static. * c-warn.cc (warn_parm_array_mismatch): Add assertion. gcc/testsuite/ChangeLog: PR c/105660 * gcc.dg/pr105660-1.c: New test. * gcc.dg/pr105660-2.c: New test. (cherry picked from commit 3057d7928c0dbc78dbf748c9621ccd102e06beee)
next prev parent reply other threads:[~2023-05-09 6:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 12:36 [Bug c/105660] New: ICE on aarch64 in warn_parm_array_mismatch julie.gaspar at sipearl dot com 2022-05-19 14:10 ` [Bug c/105660] " marxin at gcc dot gnu.org 2022-05-19 14:14 ` [Bug c/105660] [12/13 Regression] ICE in warn_parm_array_mismatch since r12-1218-gc6503fa93b5565c9 marxin at gcc dot gnu.org 2022-05-19 14:19 ` pinskia at gcc dot gnu.org 2022-05-20 6:28 ` [Bug c/105660] [12/13 Regression] ICE in warn_parm_array_mismatch when merging two function decls and VLA arguments " rguenth at gcc dot gnu.org 2022-06-22 13:05 ` romain at dolbeau dot org 2022-06-22 13:05 ` romain at dolbeau dot org 2022-10-06 15:52 ` acoplan at gcc dot gnu.org 2022-10-06 15:56 ` romain at dolbeau dot org 2022-10-06 15:58 ` acoplan at gcc dot gnu.org 2023-02-08 22:46 ` muecker at gwdg dot de 2023-02-12 19:13 ` muecker at gwdg dot de 2023-02-18 9:39 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:24 ` [Bug c/105660] [12 " rguenth at gcc dot gnu.org 2023-05-09 6:42 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-03 20:13 ` uecker 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-105660-4-0AcgjHyNws@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).