This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Is there any problem of newlib xscale memset (of assembly) code in the interrupt context.
- From: "srinivas naga vutukuri" <srinivas dot vutukuri at gmail dot com>
- To: newlib at sources dot redhat dot com
- Date: Fri, 5 Oct 2007 11:53:19 +0530
- Subject: Is there any problem of newlib xscale memset (of assembly) code in the interrupt context.
Dear All,
I am using xscale (ixp425) tool chain, and newlib is part of the
tool chain. So obviously this piece of code might have been used when
i call memset inside my application code of eCos
what could be the problem of calling this xscale assembly based
memset() code in the context of Interrupt, and that too in the 10ms
time space...
would this routine takes more time..
http://sourceware.org/cgi-bin/cvsweb.cgi/src/newlib/libc/machine/xscale/memset.c?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=src
What could be the possible difference if i use the direct coding
the routine of, and how it differs from the assembly routine...the
pro's and cons.
void *
memset(void *sp1, int c, size_t n)
{
if (n != 0) {
unsigned char *sp = sp1;
do {
*sp++ = (unsigned char)c;
} while (--n != 0);
}
return (sp1);
}
best regards,
srinivas.