From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: lib: memcpy: Do not copy to same address
Date: Mon, 23 May 2011 12:01:05 +0200 [thread overview]
Message-ID: <4DDA3061.3070408@ahsoftware.de> (raw)
In-Reply-To: <4DDA2D96.8030308@aribaud.net>
Hello,
Am 23.05.2011 11:49, schrieb Albert ARIBAUD:
>> The standard clearly say to both memory regions should not overlap when
>> memcpy() is used, so I would say this is the wrong place to fix that.
>
> I think the intent here is not to enforce the standard but to handle an
> actual, and degenerate, copy request in the most efficient manner, and
> in that respect, the patch does its job.
>
> Besides, if the patch was about enforcing the standard, then I would
> consider it highly more efficient to check the areas once in the memcpy
> function than duplicating this check before each call to the function,
> considering that the place where the copy happens is not necessarily the
> one where the source and destination were computed.
A fool proof solution would be to always use memmove() and get rid of
memcpy(). But checking for overlapped regions in memcpy() is imho the
wrong way. This just leads to more possible wrong code which uses
memcpy() when it should use memmove().
Regards,
Alexander
next prev parent reply other threads:[~2011-05-23 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 9:06 [U-Boot] [PATCH] arm: lib: memcpy: Do not copy to same address Matthias Weisser
2011-05-23 9:30 ` Alexander Holler
2011-05-23 9:46 ` Matthias Weißer
2011-05-23 9:51 ` Alexander Holler
2011-05-23 9:49 ` Albert ARIBAUD
2011-05-23 10:01 ` Alexander Holler [this message]
2011-07-26 6:02 ` Matthias Weißer
2011-08-12 8:49 ` Albert ARIBAUD
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=4DDA3061.3070408@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=u-boot@lists.denx.de \
/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