From: Xi Ruoyao <xry111@xry111.site>
To: libc-alpha@sourceware.org
Cc: caiyinyu <caiyinyu@loongson.cn>, Wang Xuerui <i@xen0n.name>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Xi Ruoyao <xry111@xry111.site>
Subject: [PATCH 3/5] string: stpcpy.c: Only alias __stpcpy to stpcpy if STPCPY undefined
Date: Sat, 15 Apr 2023 19:23:38 +0800 [thread overview]
Message-ID: <20230415112340.38431-4-xry111@xry111.site> (raw)
In-Reply-To: <20230415112340.38431-1-xry111@xry111.site>
If STPCPY is defined, it's likely __stpcpy is not provided by this file
anyway. So it does not make too much sense to make the alias.
---
string/stpcpy.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/string/stpcpy.c b/string/stpcpy.c
index dd0fef12ef..80ddf81595 100644
--- a/string/stpcpy.c
+++ b/string/stpcpy.c
@@ -116,6 +116,9 @@ STPCPY (char *dest, const char *src)
: stpcpy_unaligned_loop ((op_t*) dest,
(const op_t *) (src - ofs) , ofs);
}
+
+#ifndef STPCPY
weak_alias (__stpcpy, stpcpy)
libc_hidden_def (__stpcpy)
libc_hidden_builtin_def (stpcpy)
+#endif
--
2.39.2
next prev parent reply other threads:[~2023-04-15 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 11:23 [PATCH 0/5] LoongArch: Multiarch string and memory copy routines for unaligned access Xi Ruoyao
2023-04-15 11:23 ` [PATCH 1/5] LoongArch: Add bits/hwcap.h for Linux Xi Ruoyao
2023-04-15 11:23 ` [PATCH 2/5] LoongArch: Add LOONGARCH_HAVE_UAL macro Xi Ruoyao
2023-04-15 11:23 ` Xi Ruoyao [this message]
2023-04-15 11:23 ` [PATCH 4/5] LoongArch: Multiarch stpcpy for unaligned access Xi Ruoyao
2023-04-15 11:23 ` [PATCH 5/5] LoongArch: Multiarch memcpy " Xi Ruoyao
2023-04-18 3:01 ` [PATCH 0/5] LoongArch: Multiarch string and memory copy routines " caiyinyu
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=20230415112340.38431-4-xry111@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=i@xen0n.name \
--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).