From: Alexander Monakov <amonakov@ispras.ru>
To: Michael Matz <matz@suse.de>
Cc: gcc-patches@gcc.gnu.org, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [x86-64] RFC: Add nosse abi attribute
Date: Tue, 11 Jul 2023 18:17:35 +0300 (MSK) [thread overview]
Message-ID: <1222e0de-8260-9ba3-44fb-ec801fc3a4e2@ispras.ru> (raw)
In-Reply-To: <alpine.LSU.2.20.2307111443120.13548@wotan.suse.de>
On Tue, 11 Jul 2023, Michael Matz wrote:
> > > To that end I introduce actually two related attributes (for naming
> > > see below):
> > > * nosseclobber: claims (and ensures) that xmm8-15 aren't clobbered
> >
> > This is the weak/active form; I'd suggest "preserve_high_sse".
>
> But it preserves only the low parts :-) You swapped the two in your
> mind when writing the reply?
Ahhh. By "high SSE" I mean the high-numbered SSE regs, i.e. xmm8-15, not
the higher halves of (unspecified subset of) SSE regs.
If you look from AVX viewpoint, yes, it preserves lower 128 bits of the
high-numbered vector registers.
Alexander
next prev parent reply other threads:[~2023-07-11 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:55 Michael Matz
2023-07-10 17:28 ` Richard Biener
2023-07-10 19:07 ` Alexander Monakov
2023-07-10 20:33 ` Alexander Monakov
2023-07-11 6:42 ` Richard Biener
2023-07-11 8:53 ` Jan Hubicka
2023-07-11 9:07 ` Richard Biener
2023-07-11 13:00 ` Richard Biener
2023-07-11 13:21 ` Jan Hubicka
2023-07-11 14:00 ` Michael Matz
2023-07-11 13:59 ` Alexander Monakov
2023-07-11 14:57 ` Michael Matz
2023-07-11 15:17 ` Alexander Monakov [this message]
2023-07-11 15:34 ` Michael Matz
2023-07-11 16:53 ` Alexander Monakov
2023-07-17 23:00 ` Richard Sandiford
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=1222e0de-8260-9ba3-44fb-ec801fc3a4e2@ispras.ru \
--to=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=matz@suse.de \
/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).