Xref: utzoo comp.lang.c:12271 comp.arch:6212
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!nrl-cmf!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c,comp.arch
Subject: Re: Explanation, please!
Message-ID: <8407@smoke.ARPA>
Date: 1 Sep 88 01:34:20 GMT
References: <653@paris.ICS.UCI.EDU> <2877@ttrdc.UUCP> <ac4GLe9fit1010twl3.@amdahl.uts.amdahl.com> <682@proxftl.UUCP> <2945@wright.mips.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 7

In article <2945@wright.mips.COM> earl@mips.COM (Earl Killian) writes:
>According to the author, that code was used for copying to a 16-bit IO
>device.  It would have be illegal to use memcpy or bcopy because they
>would make word references to the device.

Wrong reason.  memcpy() etc. don't have the right behavior for stashing
a sequence of values into the same destination location.