From: Alejandro Colomar <alx@kernel.org>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
linux-man@vger.kernel.org
Subject: Re: [PATCH v3] ld.so.8: Describe glibc Hardware capabilities
Date: Tue, 24 Oct 2023 11:43:28 +0200 [thread overview]
Message-ID: <ZTeRx4vqHQ07eATQ@debian> (raw)
In-Reply-To: <CACKs7VBdNpWL6-GsECk46s7rK+aDiSr5BjROFL-T_Mh2AvPQ9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Hi Stefan,
On Tue, Oct 24, 2023 at 10:59:12AM +0300, Stefan Puiu wrote:
[...]
> > >> Signed-off-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> > >> ---
> > >> man8/ld.so.8 | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
> > >> 1 file changed, 47 insertions(+), 1 deletion(-)
[...]
>
> > .PP
> > For instance, on x86 64-bit, if the hardware supports
> > .B x86_64-v3
> > (for instance Intel Haswell or AMD Excavator)
> > , the resulting search path will be
> > .BR glibc-hwcaps/x86-64-v3:glibc-hwcaps/x86-64-v2:.
>
> I think it would be useful if the existing levels are defined
> somewhere; maybe Alex can suggest the proper manpage.
I'm sorry; I didn't even know about these things until Adhemerval sent
the patch. But yeah, I agree that if would be good to define them. :)
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-24 9:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 17:23 [PATCH v3] ld.so.8: Describe glibc Hardware capabilities Adhemerval Zanella
2023-10-19 19:10 ` Stefan Puiu
2023-10-20 17:49 ` Adhemerval Zanella Netto
2023-10-24 7:59 ` Stefan Puiu
2023-10-24 9:43 ` Alejandro Colomar [this message]
2023-10-24 10:00 ` Stefan Puiu
2023-10-24 10:53 ` Alejandro Colomar
2023-10-26 18:26 ` Adhemerval Zanella Netto
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=ZTeRx4vqHQ07eATQ@debian \
--to=alx@kernel.org \
--cc=adhemerval.zanella@linaro.org \
--cc=linux-man@vger.kernel.org \
--cc=stefan.puiu@gmail.com \
/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