From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] NEWS: Add entry for glibc-hwcaps and deprecate legacy hwcaps
Date: Fri, 29 Jan 2021 13:39:42 -0300 [thread overview]
Message-ID: <632e4446-e34f-296c-6d3b-6d5d8ec98886@linaro.org> (raw)
In-Reply-To: <87pn1nwvo0.fsf@oldenburg.str.redhat.com>
Ok for 2.33.
On 29/01/2021 13:32, Florian Weimer wrote:
> ---
> NEWS | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index d121f7df87..6521a4f5b7 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -16,6 +16,19 @@ Major new features:
> * The dynamic linker accepts the --argv0 argument and provides opportunity
> to change argv[0] string.
>
> +* The dynamic linker loads optimized implementations of shared objects
> + from subdirectories under the glibc-hwcaps directory on the library
> + search path if the system's capabilities meet the requirements for
> + that subdirectory. Initially supported subdirectories include
> + "power9" and "power10" for the powerpc64le-linux-gnu architecture,
> + "z13", "z14", "z15" for s390x-linux-gnu, and "x86-64-v2", "x86-64-v3",
> + "x86-64-v4" for x86_64-linux-gnu. In the x86_64-linux-gnu case, the
> + subsdirectory names correspond to the vendor-independent x86-64
> + microarchitecture levels defined in the x86-64 psABI supplement.
> +
> +* The new --help option of the dynamic linker provides usage and
> + information and library search path diagnostics.
> +
> * The mallinfo2 function is added to report statistics as per mallinfo,
> but with larger field widths to accurately report values that are
> larger than fit in an integer.
Ok.
> @@ -63,6 +76,14 @@ Deprecated and removed features, and other changes affecting compatibility:
> libraries that use this type in their interfaces. The new definition
> improves consistency with compiler behavior in many scenarios.
>
> +* A future version of glibc will stop loading shared objects from the
> + "tls" subdirectories on the library search path, the subdirectory that
> + corresponds to the AT_PLATFORM system name, and also stop employing
> + the legacy AT_HWCAP search mechanism. Applications should switch to
> + the new glibc-hwcaps mechanism instead; if they do not do that, only
> + the baseline version (directly from the search path directory) will be
> + loaded.
> +
> Changes to build and runtime requirements:
>
> * On Linux, the system administrator needs to configure /dev/pts with
>
Ok.
next prev parent reply other threads:[~2021-01-29 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 16:32 Florian Weimer
2021-01-29 16:39 ` Paul Zimmermann
2021-01-29 16:39 ` Adhemerval Zanella [this message]
2021-01-29 16:44 ` 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=632e4446-e34f-296c-6d3b-6d5d8ec98886@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=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).