public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] aarch64: Don't build wordcopy Date: Fri, 28 Oct 2022 10:18:17 +0000 (GMT) [thread overview] Message-ID: <20221028101817.488C33857422@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=dd31f42e39206bc69f4a60e47ee117f6c968138c commit dd31f42e39206bc69f4a60e47ee117f6c968138c Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Thu Jul 28 14:29:19 2022 +0100 aarch64: Don't build wordcopy Use an empty wordcopy.c to avoid building the generic one. It does not seem to be used anywhere. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> Diff: --- sysdeps/aarch64/wordcopy.c | 0 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/sysdeps/aarch64/wordcopy.c b/sysdeps/aarch64/wordcopy.c new file mode 100644 index 0000000000..e69de29bb2
reply other threads:[~2022-10-28 10:18 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=20221028101817.488C33857422@sourceware.org \ --to=nsz@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: linkBe 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).