public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] s390: Fix build for -march=z13
Date: Mon, 20 Feb 2023 20:16:36 +0000 (GMT) [thread overview]
Message-ID: <20230220201636.1A0A9385B51F@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8b014a1b1f7aee1e3348db108aeea396359d481e
commit 8b014a1b1f7aee1e3348db108aeea396359d481e
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Mon Feb 20 11:18:08 2023 -0300
s390: Fix build for -march=z13
It fixes the build after 7ea510127e2067e and 22999b2f0fb62.
Checked with build for s390x-linux-gnu with -march=z13.
Reviewed-by: Arjun Shankar <arjun@redhat.com>
Diff:
---
sysdeps/s390/memrchr-vx.S | 1 +
sysdeps/s390/strchrnul-vx.S | 1 +
2 files changed, 2 insertions(+)
diff --git a/sysdeps/s390/memrchr-vx.S b/sysdeps/s390/memrchr-vx.S
index c6c3168668..4080dccfbc 100644
--- a/sysdeps/s390/memrchr-vx.S
+++ b/sysdeps/s390/memrchr-vx.S
@@ -161,6 +161,7 @@ ENTRY(MEMRCHR_Z13)
END(MEMRCHR_Z13)
# if ! HAVE_MEMRCHR_IFUNC
+libc_hidden_def (__memrchr)
strong_alias (MEMRCHR_Z13, __memrchr)
weak_alias (__memrchr, memrchr)
# endif
diff --git a/sysdeps/s390/strchrnul-vx.S b/sysdeps/s390/strchrnul-vx.S
index 07f39426b7..b705979481 100644
--- a/sysdeps/s390/strchrnul-vx.S
+++ b/sysdeps/s390/strchrnul-vx.S
@@ -94,6 +94,7 @@ ENTRY(STRCHRNUL_Z13)
END(STRCHRNUL_Z13)
# if ! HAVE_STRCHRNUL_IFUNC
+libc_hidden_def (__strchrnul)
strong_alias (STRCHRNUL_Z13, __strchrnul)
weak_alias (__strchrnul, strchrnul)
# endif
reply other threads:[~2023-02-20 20:16 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=20230220201636.1A0A9385B51F@sourceware.org \
--to=azanella@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).