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/101956] Miss vectorization from v4hi to v4df Date: Wed, 18 Aug 2021 06:54:05 +0000 [thread overview] Message-ID: <bug-101956-4-Saiwbt39KP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101956 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Component|target |tree-optimization Last reconfirmed| |2021-08-18 Blocks| |53947 Status|UNCONFIRMED |NEW --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- vectorizable_conversion only checks case NONE: if (code != FIX_TRUNC_EXPR && code != FLOAT_EXPR && !CONVERT_EXPR_CODE_P (code)) return false; if (supportable_convert_operation (code, vectype_out, vectype_in, &code1)) break; /* FALLTHRU */ unsupported: if (dump_enabled_p ()) dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location, "conversion not supported by target.\n"); return false; compared to WIDEN/NARROW which supoort multi-step conversions. It shouldn't be too difficult to teach the NONE case to do this (are there any conversion instructions that do more than 2x widen/narrow?) IMHO this should be addressed at the vectorizer level. 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:[~2021-08-18 6:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-18 6:00 [Bug target/101956] New: " crazylht at gmail dot com 2021-08-18 6:11 ` [Bug target/101956] " crazylht at gmail dot com 2021-08-18 6:49 ` crazylht at gmail dot com 2021-08-18 6:54 ` rguenth at gcc dot gnu.org [this message] 2022-03-07 21:42 ` [Bug tree-optimization/101956] " pinskia at gcc dot gnu.org 2023-11-01 3:35 ` crazylht at gmail dot com
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-101956-4-Saiwbt39KP@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).