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/105058] Incorrect register constraint in KL patterns
Date: Sat, 26 Mar 2022 20:03:02 +0000	[thread overview]
Message-ID: <bug-105058-4-p3u965F8VI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105058-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:

https://gcc.gnu.org/g:f0ed5f0763933de8287b3e01aa7fd3efdd77d485

commit r11-9695-gf0ed5f0763933de8287b3e01aa7fd3efdd77d485
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Fri Mar 25 10:48:16 2022 -0700

    x86: Use x constraint on KL patterns

    Since KL instructions have no AVX512 version, replace the "v" register
    constraint with the "x" register constraint.

            PR target/105058
            * config/i386/sse.md (loadiwkey): Replace "v" with "x".
            (aes<aesklvariant>u8): Likewise.

    (cherry picked from commit ede5f5224d55b84b9f186b288164df9c06fd85e7)

  parent reply	other threads:[~2022-03-26 20:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 17:41 [Bug target/105058] New: " hjl.tools at gmail dot com
2022-03-26  6:52 ` [Bug target/105058] " crazylht at gmail dot com
2022-03-26 14:16 ` cvs-commit at gcc dot gnu.org
2022-03-26 20:03 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-26 20:04 ` hjl.tools 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-105058-4-p3u965F8VI@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).