public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Matthew Malcomson <matmal01@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/ARM/heads/morello)] testsuite: Fix morello/blockmode_copies.c test Date: Tue, 21 Sep 2021 09:14:10 +0000 (GMT) [thread overview] Message-ID: <20210921091410.6B0483858437@sourceware.org> (raw) https://gcc.gnu.org/g:ecfe3af3308c75c155c9c9d00663f9abc9407650 commit ecfe3af3308c75c155c9c9d00663f9abc9407650 Author: Alex Coplan <alex.coplan@arm.com> Date: Thu Aug 26 11:24:09 2021 +0100 testsuite: Fix morello/blockmode_copies.c test The test was calling memcpy without including <string.h>: this led to warnings since we saw an incompatible implicit definition of memcpy. Change the test to use __builtin_memcpy instead. Diff: --- gcc/testsuite/gcc.target/aarch64/morello/blockmode_copies.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/gcc/testsuite/gcc.target/aarch64/morello/blockmode_copies.c b/gcc/testsuite/gcc.target/aarch64/morello/blockmode_copies.c index 5c44b95019d..b33d73a3012 100644 --- a/gcc/testsuite/gcc.target/aarch64/morello/blockmode_copies.c +++ b/gcc/testsuite/gcc.target/aarch64/morello/blockmode_copies.c @@ -1,13 +1,13 @@ /* { dg-do compile { target aarch64*-*-* } } */ /* { dg-additional-options "-O3" } */ -void e(char *x) { memcpy(x, x + 8, 8); } +void e(char *x) { __builtin_memcpy(x, x + 8, 8); } -void f(char *x) { memcpy(x, x + 16, 16); } +void f(char *x) { __builtin_memcpy(x, x + 16, 16); } -void g(char *x) { memcpy(x, x + 32, 32); } +void g(char *x) { __builtin_memcpy(x, x + 32, 32); } -void h(char *x) { memcpy(x, x + 36, 36); } +void h(char *x) { __builtin_memcpy(x, x + 36, 36); } int fun(int x) { @@ -16,4 +16,4 @@ int fun(int x) goto *a[x++]; label2: return x; -} \ No newline at end of file +}
reply other threads:[~2021-09-21 9:14 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=20210921091410.6B0483858437@sourceware.org \ --to=matmal01@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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).