This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
help for lwl/lwr/swl/swr instructions
- From: "guo guo" <sunnyboyguo at gmail dot com>
- To: libc-ports at sourceware dot org
- Date: Fri, 10 Aug 2007 11:27:37 -0700
- Subject: help for lwl/lwr/swl/swr instructions
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TNGuPrLrsa5ovoIhi0o3NVDunt/UZyZOAzp8ZXgtDaQWucTqH/eShdRNnRd6FIoR1w+q2Ru9VXH8YQNvm3P9ZKs3v0NOI2kYMbXnUuMdgL2iGho6yhXWu8Y4eelxYEchedMlgy9dAjFVT1PT9pQ7TSNdvm3q1Lq5tzjAaPPQP+Y=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=AUuHUaWdhS0F5/ThDLaqxsup55yetvftAhyiWcYHPTzNt/9IabJ3lRMsYEvbA+5YPdKv9Mqo3iqeofGCJz6ZCs7y97EzQnzgYlKlzF2mUZWRhJpwVipoqsjyt2oqMwETM2OfDrWHsz0HelHrMBWo32tz6MvUtBMlrVoLMDb+yOA=
Dear all,
I'm busied myself about building Glibc2.5 for mips target. Our mips
chip don't support lwl/lwr/swl/swr instructions, so I applied one
patch for gcc which can avoid lwl/lwr/swl/swr instructions, and it can
work well for C source code. But some functions are implemented with
assembly language, such as memcpy() which have two versions
…/glibc/ports/sysdeps/mips/memcpy.S and /glibc/string/memcpy.c, and
memcpy.S have lwl/lwr/swl/swr instructions. I want to use memcpy.c to
try to build glibc, my question is how to configure the glibc to be
compiled with memcpy.c or memcpy.S explicitly? And is there a better
way to deal with lwl/lwr/swl/swr instructions?
Thank you very much!
Best regards,
Tony