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 tree-optimization/98365] Miss vectoization for signed char ifcvt Date: Tue, 01 Jun 2021 01:59:40 +0000 [thread overview] Message-ID: <bug-98365-4-0Q01K4Wbqb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98365-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98365 --- Comment #7 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:28daadc98094501175c9dfe4a985871fa6aa4f94 commit r12-1138-g28daadc98094501175c9dfe4a985871fa6aa4f94 Author: liuhongt <hongtao.liu@intel.com> Date: Wed Jan 6 16:33:27 2021 +0800 Extend is_cond_scalar_reduction to handle nop_expr after/before scalar reduction.[PR98365] gcc/ChangeLog: PR tree-optimization/98365 * tree-if-conv.c (strip_nop_cond_scalar_reduction): New function. (is_cond_scalar_reduction): Handle nop_expr in cond scalar reduction. (convert_scalar_cond_reduction): Ditto. (predicate_scalar_phi): Ditto. gcc/testsuite/ChangeLog: PR tree-optimization/98365 * gcc.target/i386/pr98365.c: New test.
next prev parent reply other threads:[~2021-06-01 1:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-18 1:13 [Bug tree-optimization/98365] New: Miss vectoization crazylht at gmail dot com 2021-01-05 5:09 ` [Bug tree-optimization/98365] Miss vectoization for signed char ifcvt crazylht at gmail dot com 2021-01-05 5:40 ` crazylht at gmail dot com 2021-01-05 9:01 ` rguenth at gcc dot gnu.org 2021-01-05 9:57 ` crazylht at gmail dot com 2021-01-05 10:06 ` crazylht at gmail dot com 2021-01-06 9:22 ` crazylht at gmail dot com 2021-06-01 1:59 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-01 2:01 ` crazylht at gmail dot com 2021-09-17 6:41 ` pinskia 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-98365-4-0Q01K4Wbqb@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).