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/98612] _mm_comieq_sd has wrong semantics
Date: Tue, 12 Jan 2021 03:18:44 +0000	[thread overview]
Message-ID: <bug-98612-4-l3l2s71jaD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98612-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98612

--- Comment #6 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:240f0a490dae0fb9ef72fa21a93e8088d17fb682

commit r11-6605-g240f0a490dae0fb9ef72fa21a93e8088d17fb682
Author: liuhongt <hongtao.liu@intel.com>
Date:   Mon Jan 11 14:47:49 2021 +0800

    Delete dead code in ix86_expand_sse_comi.

    d->flag is always 0 for builtins located in
    BDESC_FIRST (comi,COMI,...)
    ...
    BDESC_END (COMI, PCMPESTR)

    gcc/ChangeLog:
            PR target/98612
            * config/i386/i386-builtins.h (BUILTIN_DESC_SWAP_OPERANDS):
            Deleted.
            * config/i386/i386-expand.c (ix86_expand_sse_comi): Delete
            dead code.

  parent reply	other threads:[~2021-01-12  3:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 14:46 [Bug libstdc++/98612] New: " guillaume.piolat at gmail dot com
2021-01-09 14:47 ` [Bug libstdc++/98612] " guillaume.piolat at gmail dot com
2021-01-11  6:05 ` [Bug target/98612] " crazylht at gmail dot com
2021-01-11  6:45 ` crazylht at gmail dot com
2021-01-11  8:36 ` rguenth at gcc dot gnu.org
2021-01-11 12:54 ` guillaume.piolat at gmail dot com
2021-01-12  3:18 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-19  3:15 ` crazylht at gmail dot com
2021-01-19  7:28 ` ubizjak at gmail dot com
2023-03-24 11:20 ` andysem at mail dot ru

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-98612-4-l3l2s71jaD@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: link
Be 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).