public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Carlos O'Donell <carlos@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [COMMITTED] NEWS: Move PLT tracking slowdown to glibc 2.35.
Date: Tue, 12 Apr 2022 18:50:13 -0300	[thread overview]
Message-ID: <79ee0b63-1e5f-9bd2-a70d-145c1816bcf5@linaro.org> (raw)
In-Reply-To: <20220412172913.3335901-1-carlos@redhat.com>



On 12/04/2022 14:29, Carlos O'Donell wrote:
> In commit 063f9ba220f434c7f30dd65c4cff17c0c458a7cf the NEWS section
> was accidentally added to the glibc 2.34 NEWS section. The NEWS entry
> should have been added to glibc 2.35 which contained the committed
> fix. This moves the NEWS entry to correct section.

Oops, thanks.

> ---
>  NEWS | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/NEWS b/NEWS
> index 626eeabf5d..4b6d9de2b5 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -165,6 +165,9 @@ Major new features:
>    fortification balanced against additional runtime cost (checking non-constant
>    bounds).
>  
> +* The audit libraries will avoid unnecessary slowdown if it is not required
> +  PLT tracking (by not implementing the la_pltenter or la_pltexit callbacks).
> +
>  Deprecated and removed features, and other changes affecting compatibility:
>  
>  * On x86-64, the LD_PREFER_MAP_32BIT_EXEC environment variable support
> @@ -464,9 +467,6 @@ Major new features:
>    execute programs that do not have any dynamic dependency (that is,
>    they are statically linked).  This feature is Linux-specific.
>  
> -* The audit libraries will avoid unnecessary slowdown if it is not required
> -  PLT tracking (by not implementing the la_pltenter or la_pltexit callbacks).
> -
>  Deprecated and removed features, and other changes affecting compatibility:
>  
>  * The function pthread_mutex_consistent_np has been deprecated; programs

      reply	other threads:[~2022-04-12 21:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 17:29 Carlos O'Donell
2022-04-12 21:50 ` Adhemerval Zanella [this message]

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=79ee0b63-1e5f-9bd2-a70d-145c1816bcf5@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=carlos@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).