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/104479] [12 Regression] cond_op is combined without considering single_use Date: Fri, 11 Feb 2022 07:48:18 +0000 [thread overview] Message-ID: <bug-104479-4-DvqSPfzknm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104479-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104479 --- Comment #4 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:165947fecf4d78c7effb0f1ee15e6942d8dce4ea commit r12-7193-g165947fecf4d78c7effb0f1ee15e6942d8dce4ea Author: liuhongt <hongtao.liu@intel.com> Date: Thu Feb 10 15:42:13 2022 +0800 Add single_use to simplification (uncond_op + vec_cond -> cond_op). gcc/ChangeLog: PR tree-optimization/104479 * match.pd (uncond_op + vec_cond -> cond_op): Add single_use for the dest of uncond_op. gcc/testsuite/ChangeLog: * gcc.target/i386/pr104479.c: New test. * gcc.target/i386/cond_op_shift_w-1.c: Adjust testcase.
next prev parent reply other threads:[~2022-02-11 7:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-10 6:45 [Bug tree-optimization/104479] New: " crazylht at gmail dot com 2022-02-10 7:16 ` [Bug tree-optimization/104479] " rguenth at gcc dot gnu.org 2022-02-10 8:30 ` crazylht at gmail dot com 2022-02-10 8:32 ` rguenther at suse dot de 2022-02-11 7:48 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-11 7:52 ` 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-104479-4-DvqSPfzknm@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).