RFC: Backport architecture specific improvements to release branches

H.J. Lu hjl.tools@gmail.com
Tue Mar 29 21:21:11 GMT 2022


On Tue, Mar 29, 2022 at 12:30 PM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
>
>
> 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.

This will be included in backport.

-- 
H.J.


More information about the Libc-alpha mailing list