From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: RFC: Backport architecture specific improvements to release branches
Date: Tue, 29 Mar 2022 16:29:57 -0300 [thread overview]
Message-ID: <c07e36c0-1a6b-d412-e522-f1c807f53791@linaro.org> (raw)
In-Reply-To: <CAFUsyfL7rzNMYMxv_VLiRPMA9DYHoyeSrQwKpLOMO84Hx4SQ9Q@mail.gmail.com>
On 29/03/2022 16:19, Noah Goldstein via Libc-alpha wrote:
> On Tue, Mar 29, 2022 at 2:02 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>>
>> On Tue, Mar 29, 2022 at 10:36 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>>>
>>> On Tue, Mar 29, 2022 at 12:29 PM H.J. Lu via Libc-alpha
>>> <libc-alpha@sourceware.org> wrote:
>>>>
>>>> Hi,
>>>>
>>>> We'd like to backport architecture specific improvements to release branches,
>>>> similar to backports under sysdeps/x86_64/multiarch on users/intel/x86/2.34
>>>> branch:
>>>>
>>>> https://gitlab.com/x86-glibc/glibc/-/commits/users/intel/x86/2.34
>>>
>>> Given that the compiler does not emit `bzero` and we dropped the `__memsetzero`
>>> optimization maybe best w.o:
>>> https://gitlab.com/x86-glibc/glibc/-/commit/76e17e47789ef4faf1367b2e48c19763559c79a0
>>> for the sake of code size.
>>
>> I like to make the release branch as close to the master branch as possible
>> to make backporting easier.
>>
>
> Should we drop the optimized bzero on master? Or keep both?
As a side note, I have removed bzero optimization on all targets except x86.
It is on my plan to clean x86 as well.
next prev parent reply other threads:[~2022-03-29 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 17:28 H.J. Lu
2022-03-29 17:36 ` Noah Goldstein
2022-03-29 19:02 ` H.J. Lu
2022-03-29 19:19 ` Noah Goldstein
2022-03-29 19:29 ` Adhemerval Zanella [this message]
2022-03-29 21:21 ` H.J. Lu
2022-03-29 19:32 ` Adhemerval Zanella
2022-03-29 19:33 ` Andreas K. Huettel
2022-03-29 19:36 ` Adhemerval Zanella
2022-03-29 19:40 ` Andreas K. Huettel
2022-04-12 11:49 ` 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=c07e36c0-1a6b-d412-e522-f1c807f53791@linaro.org \
--to=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).