public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Wilco Dijkstra <wilco@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] AArch64: Sort makefile entries
Date: Tue,  7 Jun 2022 15:59:08 +0000 (GMT)	[thread overview]
Message-ID: <20220607155908.C7D7939484B3@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=eea282d9c665392d6959f6d7112ba4bef27701c9

commit eea282d9c665392d6959f6d7112ba4bef27701c9
Author: Wilco Dijkstra <wdijkstr@arm.com>
Date:   Tue Jun 7 16:45:46 2022 +0100

    AArch64: Sort makefile entries
    
    Sort makefile entries to reduce conflicts.

Diff:
---
 sysdeps/aarch64/multiarch/Makefile | 24 ++++++++++++++++++------
 1 file changed, 18 insertions(+), 6 deletions(-)

diff --git a/sysdeps/aarch64/multiarch/Makefile b/sysdeps/aarch64/multiarch/Makefile
index 490aaa0faf..16297192ee 100644
--- a/sysdeps/aarch64/multiarch/Makefile
+++ b/sysdeps/aarch64/multiarch/Makefile
@@ -1,8 +1,20 @@
 ifeq ($(subdir),string)
-sysdep_routines += memcpy_generic memcpy_advsimd memcpy_thunderx memcpy_thunderx2 \
-		   memcpy_falkor memcpy_a64fx memcpy_sve \
-		   memset_generic memset_falkor memset_emag memset_kunpeng \
-		   memset_a64fx \
-		   memchr_generic memchr_nosimd \
-		   strlen_mte strlen_asimd
+sysdep_routines += \
+  memchr_generic \
+  memchr_nosimd \
+  memcpy_a64fx \
+  memcpy_advsimd \
+  memcpy_falkor \
+  memcpy_generic \
+  memcpy_sve \
+  memcpy_thunderx \
+  memcpy_thunderx2 \
+  memset_a64fx \
+  memset_emag \
+  memset_falkor \
+  memset_generic \
+  memset_kunpeng \
+  strlen_asimd \
+  strlen_mte \
+# sysdep_routines
 endif


                 reply	other threads:[~2022-06-07 15:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220607155908.C7D7939484B3@sourceware.org \
    --to=wilco@sourceware.org \
    --cc=glibc-cvs@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).