public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110018] Missing vectorizable_conversion(unsigned char -> double) for BB vectorizer Date: Mon, 26 Jun 2023 07:49:28 +0000 [thread overview] Message-ID: <bug-110018-4-jmjyfFVVg3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110018-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110018 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:1bfe7e5352d1f4ac525317454aca45aa80a517ba commit r14-2086-g1bfe7e5352d1f4ac525317454aca45aa80a517ba Author: liuhongt <hongtao.liu@intel.com> Date: Sun Jun 25 11:12:29 2023 +0800 Use cvt_op to save intermediate type operand instead of "subtle" vec_dest. When there're multiple operands in vec_oprnds0, vec_dest will be overwrited to vectype_out, but in multi_step_cvt case, cvt_type is expected. It caused an ICE when verify_gimple_in_cfg. gcc/ChangeLog: PR tree-optimization/110371 PR tree-optimization/110018 * tree-vect-stmts.cc (vectorizable_conversion): Use cvt_op to save intermediate type operand instead of "subtle" vec_dest for case NONE. gcc/testsuite/ChangeLog: * gcc.target/aarch64/pr110371.c: New test.
prev parent reply other threads:[~2023-06-26 7:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-29 2:35 [Bug middle-end/110018] New: " crazylht at gmail dot com 2023-05-29 3:28 ` [Bug middle-end/110018] " pinskia at gcc dot gnu.org 2023-05-29 5:53 ` crazylht at gmail dot com 2023-05-29 6:14 ` crazylht at gmail dot com 2023-05-30 7:57 ` rguenth at gcc dot gnu.org 2023-05-30 9:50 ` crazylht at gmail dot com 2023-06-21 2:33 ` cvs-commit at gcc dot gnu.org 2023-06-21 2:38 ` crazylht at gmail dot com 2023-06-21 14:35 ` cvs-commit at gcc dot gnu.org 2023-06-26 7:30 ` cvs-commit at gcc dot gnu.org 2023-06-26 7:49 ` cvs-commit at gcc dot gnu.org [this message]
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-110018-4-jmjyfFVVg3@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).