From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] ld.so: Implement the --list-diagnostics option
Date: Mon, 01 Mar 2021 10:12:40 +0100 [thread overview]
Message-ID: <877dmrjkzb.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <875z2hshtn.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Wed, 24 Feb 2021 14:42:28 +0100")
I'd appreciate a review of this.
<https://sourceware.org/pipermail/libc-alpha/2021-February/122973.html>
<https://sourceware.org/pipermail/libc-alpha/2021-February/122972.html>
I think this, or something very much like it, will be needed to diagnose
glibc-hwcaps and IFUNC selection issues.
Thanks,
Florian
next prev parent reply other threads:[~2021-03-01 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 13:42 Florian Weimer
2021-02-24 13:43 ` [PATCH 2/2] x86: Add CPU-specific diagnostics to ld.so --list-diagnostics Florian Weimer
2021-03-01 23:20 ` H.J. Lu
2021-03-02 6:32 ` Florian Weimer
2021-03-01 9:12 ` Florian Weimer [this message]
2021-03-01 23:13 ` [PATCH 1/2] ld.so: Implement the --list-diagnostics option H.J. Lu
2021-03-02 6:00 ` Florian Weimer
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=877dmrjkzb.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.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).