public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/31371] x86-64: APX and Tile registers aren't preserved in ld.so trampoline
Date: Fri, 08 Mar 2024 20:02:31 +0000 [thread overview]
Message-ID: <bug-31371-131-t1Ogl2Z2uP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31371-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31371
--- Comment #8 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to H.J. Lu from comment #7)
> Do we need to backport the fixes to release branches?
I think it's a necessary correctness fix, but it's not risk-free due to
increased stack size requirement. But it's the same as with lazy binding, so
hopefully it should be okay.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-08 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 18:21 [Bug dynamic-link/31371] New: APX " hjl.tools at gmail dot com
2024-02-11 19:38 ` [Bug dynamic-link/31371] " fweimer at redhat dot com
2024-02-11 19:39 ` [Bug dynamic-link/31371] x86-64: " fweimer at redhat dot com
2024-02-11 19:44 ` hjl.tools at gmail dot com
2024-02-11 20:56 ` fw at deneb dot enyo.de
2024-02-11 22:21 ` hjl.tools at gmail dot com
2024-02-15 21:14 ` [Bug dynamic-link/31371] x86-64: APX and Tile " hjl.tools at gmail dot com
2024-02-25 17:22 ` cvs-commit at gcc dot gnu.org
2024-03-08 19:58 ` carlos at redhat dot com
2024-03-08 19:59 ` hjl.tools at gmail dot com
2024-03-08 20:02 ` fweimer at redhat dot com [this message]
2024-04-01 17:39 ` cvs-commit at gcc dot gnu.org
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-31371-131-t1Ogl2Z2uP@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).