From: Tad Hunt <tad@entrisphere.com>
To: 9fans@cse.psu.edu
Subject: [9fans] more libc/power assembly bits
Date: Thu, 3 Jul 2003 18:58:00 -0700 [thread overview]
Message-ID: <MOBYDICKUuEhjJ8uT6S000000fe@mobydick.int.entrisphere.com> (raw)
Two more assembler goodies: strchr() and strlen().
NetBSD has an even more optimized strlen(). According to the
comment at the top it originated in 'The PowerPC Compiler Writer's
Guide', by Steve Hoxey, Faraydon Karim, Bill Hay and Hank Warren.
(http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libc/arch/powerpc/string/strlen.S?rev=1.2)
However, it would have been way too much work to convert the powerpc
assembly source into qa(1) source.
In any case, these ones should be faster than the C versions from
the libc/port directory.
-Tad
# text/plain; name="strlen.s" [ strlen.s ] /usr/home/tad/R1.2.0/plan9/src/libc/power/strlen.s
# text/plain; name="strchr.s" [ strchr.s ] /usr/home/tad/R1.2.0/plan9/src/libc/power/strchr.s
reply other threads:[~2003-07-04 1:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MOBYDICKUuEhjJ8uT6S000000fe@mobydick.int.entrisphere.com \
--to=tad@entrisphere.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).