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/107061] ENCODEKEY128 clobbers xmm4-xmm6
Date: Thu, 29 Sep 2022 18:32:11 +0000	[thread overview]
Message-ID: <bug-107061-4-tmQUtw7mkc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107061-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r12-8795-gf1454a75c9a165c0ba30833f23f799044fd7a7fe
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Tue Sep 27 16:19:11 2022 -0700

    i386: Mark XMM4-XMM6 as clobbered by encodekey128/encodekey256

    encodekey128 and encodekey256 operations clear XMM4-XMM6.  But it is
    documented that XMM4-XMM6 are reserved for future usages and software
    should not rely upon them being zeroed.  Change encodekey128 and
    encodekey256 to clobber XMM4-XMM6.

    gcc/

            PR target/107061
            * config/i386/predicates.md (encodekey128_operation): Check
            XMM4-XMM6 as clobbered.
            (encodekey256_operation): Likewise.
            * config/i386/sse.md (encodekey128u32): Clobber XMM4-XMM6.
            (encodekey256u32): Likewise.

    gcc/testsuite/

            PR target/107061
            * gcc.target/i386/keylocker-encodekey128.c: Don't check
            XMM4-XMM6.
            * gcc.target/i386/keylocker-encodekey256.c: Likewise.

    (cherry picked from commit db288230db55dc1ff626f46c708b555847013a41)

  parent reply	other threads:[~2022-09-29 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 19:29 [Bug target/107061] New: " hjl.tools at gmail dot com
2022-09-28 18:16 ` [Bug target/107061] " cvs-commit at gcc dot gnu.org
2022-09-29 18:32 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-29 18:57 ` cvs-commit at gcc dot gnu.org
2022-09-29 18:58 ` 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-107061-4-tmQUtw7mkc@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).