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 target/98567] Failure to optimize using ZF flag from blsi Date: Thu, 07 Jan 2021 16:20:40 +0000 [thread overview] Message-ID: <bug-98567-4-mpgJ2fj6hL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98567-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98567 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:6bca2ebf10654b8beb5c5737c8652e8262901294 commit r11-6520-g6bca2ebf10654b8beb5c5737c8652e8262901294 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Jan 7 17:18:58 2021 +0100 i386: Optimize blsi followed by comparison [PR98567] The BLSI instruction sets SF and ZF based on the result and clears OF. CF is set to something unrelated. The following patch optimizes BLSI followed by comparison, so we don't need to emit a TEST insn in between. 2021-01-07 Jakub Jelinek <jakub@redhat.com> PR target/98567 * config/i386/i386.md (*bmi_blsi_<mode>_cmp, *bmi_blsi_<mode>_ccno): New define_insn patterns. * gcc.target/i386/pr98567-1.c: New test. * gcc.target/i386/pr98567-2.c: New test.
next prev parent reply other threads:[~2021-01-07 16:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-06 16:32 [Bug target/98567] New: " gabravier at gmail dot com 2021-01-06 16:48 ` [Bug target/98567] " jakub at gcc dot gnu.org 2021-01-06 16:58 ` jakub at gcc dot gnu.org 2021-01-06 18:55 ` ubizjak at gmail dot com 2021-01-07 16:20 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-07 16:22 ` jakub 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-98567-4-mpgJ2fj6hL@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).