public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107061] New: ENCODEKEY128 clobbers xmm4-xmm6
Date: Tue, 27 Sep 2022 19:29:16 +0000 [thread overview]
Message-ID: <bug-107061-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107061
Bug ID: 107061
Summary: ENCODEKEY128 clobbers xmm4-xmm6
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: crazylht at gmail dot com, wwwhhhyyy333 at gmail dot com
Target Milestone: ---
Target: i386
The current ENCODEKEY128 clears xmm4-xmm6. But Intel key lock spec has
XMM4 through XMM6 are reserved for future usages and software should not
rely upon them being zeroed.
xmm4-xmm6 should be marked as clobbered, not zeroed for future compatibility.
next reply other threads:[~2022-09-27 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 19:29 hjl.tools at gmail dot com [this message]
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
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@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).