public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: Renlin Li <renlin.li@foss.arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	richard.sandiford@arm.com
Subject: Re: [PATCH][Testsuite] Use user defined memmove in gcc.c-torture/execute/builtins/memops-asm-lib.c
Date: Fri, 23 Jun 2017 15:27:00 -0000	[thread overview]
Message-ID: <67beba0f-5c33-871e-05b1-3244fbb752d6@gmail.com> (raw)
In-Reply-To: <594CDD3A.9090902@foss.arm.com>

On 06/23/2017 03:19 AM, Renlin Li wrote:
> Hi all,
>
> After the change r249278. bcopy is folded into memmove. And in newlib
> aarch64
> memmove implementation, it will call memcpy in certain conditions.
> The memcpy defined in memops-asm-lib.c will abort when the test is running.
>
> In this case, I defined a user memmove function which by pass the
> library one.
> So that memcpy won't be called accidentally.
>
> Okay to commit?

Having memmove call memcpy when there is no overlap seems like
a valid transformation.  I don't know which test specifically
fails so the question on my mind is whether it perhaps is overly
restrictive in assuming that this transformation must never take
place.  Other than that, although I can't really approve patches,
this one looks okay to me.  Thanks for getting to the bottom of
the failure and fixing it!

Martin

>
> gcc/testsuite/ChangeLog:
>
> 2017-06-22  Renlin Li  <renlin.li@arm.com>
>         Szabolcs Nagy  <szabolcs.nagy@arm.com>
>
>     * gcc.c-torture/execute/builtins/memops-asm-lib.c (my_memmove): New.
>     * gcc.c-torture/execute/builtins/memops-asm.c (memmove): Declare
> memmove.

  reply	other threads:[~2017-06-23 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  9:20 Renlin Li
2017-06-23 15:27 ` Martin Sebor [this message]
2017-06-23 16:10   ` Renlin Li
2017-06-23 17:11 ` Jeff Law
2017-08-06  8:45 ` Tom de Vries

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=67beba0f-5c33-871e-05b1-3244fbb752d6@gmail.com \
    --to=msebor@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=renlin.li@foss.arm.com \
    --cc=richard.sandiford@arm.com \
    /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).