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++/105946] [12 Regression] ICE in maybe_warn_pass_by_reference, at tree-ssa-uninit.cc:843 Date: Tue, 19 Jul 2022 11:37:58 +0000 [thread overview] Message-ID: <bug-105946-4-FzGQnEiYgU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105946-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105946 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:92aa9490315d969d6e7580fb6e8d006415877bd6 commit r12-8577-g92aa9490315d969d6e7580fb6e8d006415877bd6 Author: Richard Biener <rguenther@suse.de> Date: Tue Jun 14 11:10:13 2022 +0200 tree-optimization/105946 - avoid accessing excess args from uninit diag uninit diagnostics uses passing via reference and access attributes but that iterates over function type arguments which can in some cases appearantly outrun the actual arguments leading to ICEs. The following simply ignores not present arguments. 2022-06-14 Richard Biener <rguenther@suse.de> PR tree-optimization/105946 * tree-ssa-uninit.cc (maybe_warn_pass_by_reference): Do not look at arguments not specified in the function call. (cherry picked from commit e07a876c07601e1f3a27420f7d055d20193c362c)
next prev parent reply other threads:[~2022-07-19 11:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-13 12:58 [Bug c++/105946] New: [12/13 " gscfq@t-online.de 2022-06-14 9:09 ` [Bug c++/105946] " rguenth at gcc dot gnu.org 2022-06-14 10:53 ` cvs-commit at gcc dot gnu.org 2022-06-14 10:54 ` [Bug c++/105946] [12 " rguenth at gcc dot gnu.org 2022-07-15 11:21 ` marxin at gcc dot gnu.org 2022-07-19 11:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-19 11:38 ` rguenth 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-105946-4-FzGQnEiYgU@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).