public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112618] [13/14 Regression] internal compiler error: in expand_MASK_CALL, at internal-fn.cc:4529 Date: Mon, 20 Nov 2023 10:14:36 +0000 [thread overview] Message-ID: <bug-112618-4-Oar7Z4ir2B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112618-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112618 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Blocks| |53947 Status|NEW |ASSIGNED Version|unknown |13.2.1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. We're not marking the .MASK_CALL as relevant which is possibly OK since 'bar' is const. But we also fail to elide it. /* For if-conversion of inbranch SIMD clones. */ DEF_INTERNAL_FN (MASK_CALL, ECF_NOVOPS, NULL) ECF_NOVOPS is a bit heavy. We're "removing" scalar stmts in some places but do not care about not relevant ones. I have a patch. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations
next prev parent reply other threads:[~2023-11-20 10:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-19 12:13 [Bug tree-optimization/112618] New: " hubicka at gcc dot gnu.org 2023-11-19 19:29 ` [Bug tree-optimization/112618] [13/14 Regression] " pinskia at gcc dot gnu.org 2023-11-20 10:14 ` rguenth at gcc dot gnu.org [this message] 2023-11-20 14:01 ` cvs-commit at gcc dot gnu.org 2023-11-20 14:03 ` [Bug tree-optimization/112618] [13 " rguenth at gcc dot gnu.org 2024-02-06 13:20 ` cvs-commit at gcc dot gnu.org 2024-02-06 13:21 ` 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-112618-4-Oar7Z4ir2B@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).