From: Sunil Pandey <skpgkp2@gmail.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2 04/11] x86_64: Remove bcopy optimizations
Date: Thu, 12 May 2022 12:28:13 -0700 [thread overview]
Message-ID: <CAMAf5_c2yiuXOSD_RRnfv3Xov9q-LUzEKH6WvmtAYFjxrAXTWg@mail.gmail.com> (raw)
In-Reply-To: <20220223140921.2768062-5-adhemerval.zanella@linaro.org>
On Wed, Feb 23, 2022 at 6:12 AM Adhemerval Zanella via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> The symbols is not present in current POSIX specification and compiler
> already generates memmove call.
> ---
> sysdeps/x86_64/multiarch/bcopy.S | 7 -------
> 1 file changed, 7 deletions(-)
> delete mode 100644 sysdeps/x86_64/multiarch/bcopy.S
>
> diff --git a/sysdeps/x86_64/multiarch/bcopy.S b/sysdeps/x86_64/multiarch/bcopy.S
> deleted file mode 100644
> index 639f02bde3..0000000000
> --- a/sysdeps/x86_64/multiarch/bcopy.S
> +++ /dev/null
> @@ -1,7 +0,0 @@
> -#include <sysdep.h>
> -
> - .text
> -ENTRY(bcopy)
> - xchg %rdi, %rsi
> - jmp __libc_memmove /* Branch to IFUNC memmove. */
> -END(bcopy)
> --
> 2.32.0
>
I would like to backport this patch to release branches.
Any comments or objections?
--Sunil
next prev parent reply other threads:[~2022-05-12 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 14:09 [PATCH v2 00/11] Remove bcopy and bzero optimizations Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 01/11] ia64: Remove bcopy Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 02/11] powerpc: Remove bcopy optimizations Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 03/11] i386: " Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 04/11] x86_64: " Adhemerval Zanella
2022-05-12 19:28 ` Sunil Pandey [this message]
2022-02-23 14:09 ` [PATCH v2 05/11] alpha: Remove bzero optimization Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 06/11] ia64: " Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 07/11] sparc: " Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 08/11] powerpc: Remove powerpc32 bzero optimizations Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 09/11] powerpc: Remove powerpc64 " Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 10/11] s390: Remove " Adhemerval Zanella
2022-02-23 14:09 ` [PATCH v2 11/11] i686: " Adhemerval Zanella
2022-02-23 14:13 ` [PATCH v2 00/11] Remove bcopy and " Adhemerval Zanella
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=CAMAf5_c2yiuXOSD_RRnfv3Xov9q-LUzEKH6WvmtAYFjxrAXTWg@mail.gmail.com \
--to=skpgkp2@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@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).