From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: gcc builtin memcpy is bogus?
Date: Mon, 08 Dec 2003 20:27:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107091551518624@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107090003129207@msgid-missing>
On Mon, Dec 08, 2003 at 05:25:27PM +0100, Andreas Schwab wrote:
> - Don't use the casted address, but rather the original pointer in the
> memcpy call.
Thanks, that works nicely.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
prev parent reply other threads:[~2003-12-08 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 16:01 gcc builtin memcpy is bogus? Matthew Wilcox
2003-12-08 16:25 ` Andreas Schwab
2003-12-08 17:29 ` David Mosberger
2003-12-08 20:27 ` Matthew Wilcox [this message]
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=marc-linux-ia64-107091551518624@msgid-missing \
--to=willy@debian.org \
--cc=linux-ia64@vger.kernel.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