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/31501] _dl_tlsdesc_dynamic_xsavec may clobber %rbx
Date: Sat, 16 Mar 2024 14:35:14 +0000 [thread overview]
Message-ID: <bug-31501-131-v298siMsbY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31501-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31501
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=2269799
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-16 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 14:23 [Bug dynamic-link/31501] New: " fweimer at redhat dot com
2024-03-16 14:23 ` [Bug dynamic-link/31501] " fweimer at redhat dot com
2024-03-16 14:35 ` fweimer at redhat dot com [this message]
2024-03-16 14:48 ` hjl.tools at gmail dot com
2024-03-16 17:05 ` hjl.tools at gmail dot com
2024-03-17 4:00 ` sam at gentoo dot org
2024-03-17 8:12 ` fweimer at redhat dot com
2024-03-17 10:39 ` hjl.tools at gmail dot com
2024-03-17 10:43 ` sam at gentoo dot org
2024-03-17 10:57 ` sam at gentoo dot org
2024-03-17 16:28 ` hjl.tools at gmail dot com
2024-03-19 2:46 ` cvs-commit at gcc dot gnu.org
2024-03-19 2:46 ` hjl.tools at gmail dot com
2024-03-20 15:37 ` fweimer at redhat dot com
2024-04-02 13:17 ` carlos at redhat dot com
2024-04-03 17:43 ` 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-31501-131-v298siMsbY@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).