public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103686] ICE in rs6000_expand_new_builtin at rs6000-call.c:15946 Date: Tue, 14 Dec 2021 16:02:45 +0000 [thread overview] Message-ID: <bug-103686-4-AmtFTtYV0s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103686-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103686 --- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> --- Maybe something like this untested patch: diff --git a/gcc/config/rs6000/rs6000-call.c b/gcc/config/rs6000/rs6000-call.c index d9736eaf21c..c7babefa32d 100644 --- a/gcc/config/rs6000/rs6000-call.c +++ b/gcc/config/rs6000/rs6000-call.c @@ -13615,12 +13615,14 @@ rs6000_gimple_fold_new_builtin (gimple_stmt_iterator *gsi) const char *fn_name2 = (icode != CODE_FOR_nothing) ? get_insn_name ((int) icode) : "nothing"; + unsigned attr = rs6000_builtin_info[fn_code].attr; if (TARGET_DEBUG_BUILTIN) fprintf (stderr, "rs6000_gimple_fold_new_builtin %d %s %s\n", fn_code, fn_name1, fn_name2); - if (!rs6000_fold_gimple) + if ((attr & RS6000_BTC_GIMPLE) == 0 + && !rs6000_fold_gimple) return false; /* Prevent gimple folding for code that does not have a LHS, unless it is Same thing needs to happen to rs6000_gimple_fold_builtin too
next prev parent reply other threads:[~2021-12-14 16:02 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-13 13:54 [Bug target/103686] New: " marxin at gcc dot gnu.org 2021-12-13 13:54 ` [Bug target/103686] " marxin at gcc dot gnu.org 2021-12-13 14:54 ` wschmidt at gcc dot gnu.org 2021-12-14 15:49 ` bergner at gcc dot gnu.org 2021-12-14 16:02 ` bergner at gcc dot gnu.org [this message] 2021-12-14 16:52 ` wschmidt at gcc dot gnu.org 2021-12-14 16:53 ` wschmidt at gcc dot gnu.org 2021-12-14 17:00 ` wschmidt at gcc dot gnu.org 2022-01-04 10:00 ` rguenth at gcc dot gnu.org 2022-01-04 10:15 ` segher at gcc dot gnu.org 2022-01-04 15:18 ` bergner at gcc dot gnu.org 2022-01-19 22:19 ` wschmidt at gcc dot gnu.org 2022-01-20 16:19 ` willschm at gcc dot gnu.org 2022-02-03 17:17 ` cvs-commit at gcc dot gnu.org 2022-02-03 17:24 ` wschmidt 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-103686-4-AmtFTtYV0s@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).