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/95218] [11 Regression] FAIL: gcc.target/i386/fma_run_double_1.c execution test since r11-455-g94f687bd9ae37ece
Date: Wed, 20 May 2020 23:53:45 +0000	[thread overview]
Message-ID: <bug-95218-4-jwyA3WlyU1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95218-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>:

https://gcc.gnu.org/g:7797f5ec58078523a452e5cf239596e13d77d885

commit r11-535-g7797f5ec58078523a452e5cf239596e13d77d885
Author: Uros Bizjak <ubizjak@gmail.com>
Date:   Thu May 21 01:53:09 2020 +0200

    i386: Do not use commutative operands with (use) RTX [PR95238]

    2020-05-21  Uroš Bizjak  <ubizjak@gmail.com>

    gcc/ChangeLog:
            PR target/95218

            * config/i386/mmx.md (*mmx_<code>v2sf): Do not mark
            operands 1 and 2 commutative.  Manually swap operands.
            (*mmx_nabsv2sf2): Ditto.

            Partially revert:

            * config/i386/i386.md (*<code>tf2_1):
            Mark operands 1 and 2 commutative.
            (*nabstf2_1): Ditto.
            * config/i386/sse.md (*<code><mode>2): Mark operands 1 and 2
            commutative.  Do not swap operands.
            (*nabs<mode>2): Ditto.

  parent reply	other threads:[~2020-05-20 23:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:31 [Bug target/95218] New: [11 Regression] FAIL: gcc.target/i386/fma_run_double_1.c execution test msebor at gcc dot gnu.org
2020-05-19 18:37 ` [Bug target/95218] " msebor at gcc dot gnu.org
2020-05-20  6:27 ` rguenth at gcc dot gnu.org
2020-05-20 10:02 ` [Bug target/95218] [11 Regression] FAIL: gcc.target/i386/fma_run_double_1.c execution test since r11-455-g94f687bd9ae37ece marxin at gcc dot gnu.org
2020-05-20 11:07 ` ubizjak at gmail dot com
2020-05-20 11:13 ` marxin at gcc dot gnu.org
2020-05-20 12:17 ` ubizjak at gmail dot com
2020-05-20 12:22 ` ubizjak at gmail dot com
2020-05-20 12:29 ` marxin at gcc dot gnu.org
2020-05-20 12:50 ` ubizjak at gmail dot com
2020-05-20 13:05 ` rguenther at suse dot de
2020-05-20 13:13 ` rguenth at gcc dot gnu.org
2020-05-20 13:49 ` ubizjak at gmail dot com
2020-05-20 14:04 ` jakub at gcc dot gnu.org
2020-05-20 14:05 ` ubizjak at gmail dot com
2020-05-20 14:17 ` ubizjak at gmail dot com
2020-05-20 22:04 ` law at redhat dot com
2020-05-20 22:49 ` ubizjak at gmail dot com
2020-05-20 22:55 ` ubizjak at gmail dot com
2020-05-20 23:53 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-22 10:35 ` rguenth 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-95218-4-jwyA3WlyU1@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).