From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] x86-64: Update _dl_tlsdesc_dynamic to preserve vector registers
Date: Mon, 12 Feb 2024 14:29:59 +0100 [thread overview]
Message-ID: <87plx1byjs.fsf@oldenburg3.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOq8cWw3FvQChaBi+u9woGtOE3pLvXNrfdr-9X_dYRo8SA@mail.gmail.com> (H. J. Lu's message of "Mon, 12 Feb 2024 04:34:22 -0800")
* H. J. Lu:
>> the TLSDESC call? Or does current GCC already assume that all scalar
>> registers are preserved?
>
> GCC assumes that only FLAGS_REG is reserved and RAX is the destination
> register. Everything else must be preserved.
>
>> The other way to fix this is to preallocate everything, so that the need
>> for the slow path goes away.
>
> True.
I susppose we could start saving pretty much all register state for now,
and announce a plan to move to TLS data preallocation later, globally,
for all architectures.
That would need agreement from all active architecture maintainers,
though.
Thanks,
Florian
prev parent reply other threads:[~2024-02-12 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 3:19 H.J. Lu
2024-02-12 10:44 ` Florian Weimer
2024-02-12 12:34 ` H.J. Lu
2024-02-12 13:29 ` Florian Weimer [this message]
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=87plx1byjs.fsf@oldenburg3.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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).