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/105175] [12 Regression] Pointless warning about missed vector optimization Date: Wed, 06 Apr 2022 08:49:47 +0000 [thread overview] Message-ID: <bug-105175-4-4krmCs80lB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105175-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- So vectorizable_operation correctly says target_support_p == false and then goes on with target_support_p = (optab_handler (optab, vec_mode) != CODE_FOR_nothing); } bool using_emulated_vectors_p = vect_emulated_vector_p (vectype); if (!target_support_p) { if (dump_enabled_p ()) dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location, "op not supported by target.\n"); /* Check only during analysis. */ if (maybe_ne (GET_MODE_SIZE (vec_mode), UNITS_PER_WORD) || (!vec_stmt && !vect_can_vectorize_without_simd_p (code))) return false; if (dump_enabled_p ()) dump_printf_loc (MSG_NOTE, vect_location, "proceeding using word mode.\n"); using_emulated_vectors_p = true; using emulated (word-mode) vectors. In the end it will still emit code using v2si types which will have V2SImode. For those it will rely on vector lowering to perform this very lowering. So the vectorization works as desired and the lowering as well. But I agree the diagnostic in this case is questionable.
next prev parent reply other threads:[~2022-04-06 8:49 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-06 7:00 [Bug rtl-optimization/105175] New: " krebbel at gcc dot gnu.org 2022-04-06 8:17 ` [Bug tree-optimization/105175] " rguenth at gcc dot gnu.org 2022-04-06 8:30 ` krebbel at gcc dot gnu.org 2022-04-06 8:49 ` rguenth at gcc dot gnu.org [this message] 2022-04-06 9:17 ` rguenth at gcc dot gnu.org 2022-04-08 6:34 ` cvs-commit at gcc dot gnu.org 2022-04-08 6:35 ` 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-105175-4-4krmCs80lB@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).