public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102788] [12 Regression] Wrong code with -O3 Date: Fri, 15 Oct 2021 20:15:12 +0000 [thread overview] Message-ID: <bug-102788-4-YmolP0RJb8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102788-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102788 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. ... mask__43.21_62 = vect_cst__60 != vect_cst__61; _43 = var_12.0_1 != 0; _3 = (long long unsigned int) _43; vect_patt_34.22_63 = VIEW_CONVERT_EXPR<vector(4) unsigned char>(mask__43.21_62); _26 = (unsigned char) _3; Somehow the vectorizer missed the conversion but has the conversion there. /app/example.cpp:19:23: note: add new stmt: mask__43.21_62 = vect_cst__60 != vect_cst__61; /app/example.cpp:19:23: note: ------>vectorizing statement: _3 = (long long unsigned int) _43; /app/example.cpp:19:23: note: ------>vectorizing statement: patt_34 = (unsigned char) _43; /app/example.cpp:19:23: note: transform statement. /app/example.cpp:19:23: note: vect_is_simple_use: operand var_12.0_1 != 0, type of def: internal /app/example.cpp:19:23: note: vect_is_simple_use: vectype vector(4) <signed-boolean:8> /app/example.cpp:19:23: note: transform assignment. /app/example.cpp:19:23: note: vect_get_vec_defs_for_operand: _43 /app/example.cpp:19:23: note: vect_is_simple_use: operand var_12.0_1 != 0, type of def: internal /app/example.cpp:19:23: note: def_stmt = _43 = var_12.0_1 != 0; /app/example.cpp:19:23: note: add new stmt: vect_patt_34.22_63 = VIEW_CONVERT_EXPR<vector(4) unsigned char>(mask__43.21_62); /app/example.cpp:19:23: note: extracting lane for live stmt _26 = (unsigned char) _3;
next prev parent reply other threads:[~2021-10-15 20:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-15 19:54 [Bug tree-optimization/102788] New: " vsevolod.livinskij at frtk dot ru 2021-10-15 19:59 ` [Bug tree-optimization/102788] [12 Regression] " pinskia at gcc dot gnu.org 2021-10-15 20:07 ` jakub at gcc dot gnu.org 2021-10-15 20:15 ` pinskia at gcc dot gnu.org [this message] 2021-10-15 20:16 ` pinskia at gcc dot gnu.org 2021-10-18 6:29 ` rguenth at gcc dot gnu.org 2021-10-18 8:38 ` rguenth at gcc dot gnu.org 2021-10-18 8:40 ` rguenth at gcc dot gnu.org 2021-10-18 10:57 ` cvs-commit at gcc dot gnu.org 2021-10-18 11:01 ` [Bug tree-optimization/102788] [11 " rguenth at gcc dot gnu.org 2021-11-08 12:35 ` rguenth at gcc dot gnu.org 2021-11-08 12:35 ` cvs-commit 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-102788-4-YmolP0RJb8@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).