Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!ig!uwmcsd1!marque!gryphon!vector!chip
From: chip@vector.UUCP (Chip Rosenthal)
Newsgroups: comp.os.minix
Subject: Re: memcpy(3) & friends
Message-ID: <557@vector.UUCP>
Date: 14 Sep 88 21:53:33 GMT
References: <496@uvicctr.UUCP>
Reply-To: chip@vector.UUCP (Chip Rosenthal)
Organization: Dallas Semiconductor
Lines: 16

In article <496@uvicctr.UUCP> tholm@uvicctr.UUCP (Terrence W. Holm) writes:
>There follows an implementation of memcpy(3), memccpy(3),
>memchr(3), memcmp(3) and memset(3) for MINIX. Please consider
>this public domain software. "man" pages are included.

It might worth playing some games with these.  I would think that memcpy()
is one of the cases where you are willing to give a little ugliness for
performance.

There was a recent discussion in comp.lang.c about using "Duff's Device"
for loop-unrolling in a portable way.  Tom Duff himself talked about the
origins of this in <8144@alice.UUCP>.  It might be interesting to look
at this way of doing memcpy().  (I've archived a copy of Tom's message
in case anybody is interested.)
-- 
Chip Rosenthal     chip@vector.UUCP | I've been a wizard since my childhood.
Dallas Semiconductor   214-450-0486 | And I've earned some respect for my art.