public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101741] [12 Regression] ICE in fold_stmt, at gimple-range-fold.cc:541 since r12-2517-g1ce0b26e6e1e6c34 Date: Mon, 09 Aug 2021 20:26:09 +0000 [thread overview] Message-ID: <bug-101741-4-2fhghr0AFn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101741-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101741 Andrew Macleod <amacleod at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Andrew Macleod <amacleod at redhat dot com> --- Yeah, we aren't expecting the parameter and the LHS to be different. Why do we mark this as a builtin function if it doesn't match the parameter list? Regardless, when folding the call we assumed the parameter type matches the LHS. This patch changes it so if the types do not match, we will assume nothing about the function instead.
next prev parent reply other threads:[~2021-08-09 20:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 6:41 [Bug tree-optimization/101741] New: [12 Regression] ICE in fold_stmt, at gimple-range-fold.cc:541 asolokha at gmx dot com 2021-08-03 11:33 ` [Bug tree-optimization/101741] [12 Regression] ICE in fold_stmt, at gimple-range-fold.cc:541 since r12-2517-g1ce0b26e6e1e6c34 marxin at gcc dot gnu.org 2021-08-03 11:46 ` asolokha at gmx dot com 2021-08-03 11:55 ` marxin at gcc dot gnu.org 2021-08-03 20:05 ` msebor at gcc dot gnu.org 2021-08-09 20:25 ` cvs-commit at gcc dot gnu.org 2021-08-09 20:26 ` amacleod at redhat dot com [this message] 2022-11-28 22:51 ` 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-101741-4-2fhghr0AFn@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).