public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v1] NEWS: Add entry for x86-64 ISA level build
Date: Wed, 27 Jul 2022 20:10:42 +0800	[thread overview]
Message-ID: <CAFUsyfJYb9ghANKt+EMn9nx+bJdTeeViC_CwgOfwEOH7oi6z4g@mail.gmail.com> (raw)
In-Reply-To: <cb62378b-c8ca-64b9-7d95-728985a8925e@linaro.org>

On Wed, Jul 27, 2022 at 7:18 PM Adhemerval Zanella Netto via
Libc-alpha <libc-alpha@sourceware.org> wrote:
>
>
>
> On 27/07/22 03:58, Noah Goldstein via Libc-alpha wrote:
> > ---
> >  NEWS | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/NEWS b/NEWS
> > index 5827b206d9..4264a4cfc6 100644
> > --- a/NEWS
> > +++ b/NEWS
> > @@ -72,6 +72,10 @@ Major new features:
> >
> >    The LoongArch ABI is 64-bit little-endian.
> >
> > +* Support building x86-64 with multiple ISA levels.  Higher ISA levels
> > +  will use better optimized functions in the dynamic loader and
> > +  non-multiarch build as well as reduce the size of libc.so.
>
> The initial sentence sounds terse, maybe "Support for building x86-64 with
> multiple ISA levels has been added".
>

Sure. Done in V2.
> > +
> >  Deprecated and removed features, and other changes affecting compatibility:
> >
> >  * Support for prelink will be removed in the next release; this includes'
>

  reply	other threads:[~2022-07-27 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  6:58 Noah Goldstein
2022-07-27 11:18 ` Adhemerval Zanella Netto
2022-07-27 12:10   ` Noah Goldstein [this message]
2022-07-27 12:10 ` [PATCH v2] " Noah Goldstein
2022-07-27 13:48   ` Adhemerval Zanella Netto
2022-07-27 16:11   ` Joseph Myers
2022-07-27 16:22     ` Noah Goldstein
2022-07-27 16:44       ` 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=CAFUsyfJYb9ghANKt+EMn9nx+bJdTeeViC_CwgOfwEOH7oi6z4g@mail.gmail.com \
    --to=goldstein.w.n@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --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).