From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: test framework
Date: Fri, 29 Jul 2011 15:18:39 +0200 [thread overview]
Message-ID: <20110729131839.GI29562@port70.net> (raw)
now that cluts has many tests i was started to
think how to put these into a framework so it's
easy to add new tests
imho it is a tiny bit more convenient than just
writing functions which return nonzero on error
i also added benchmarking support now
(some tests and benchmarks were added from
libc-testsuit and libc-bench)
http://repo.or.cz/w/musl-test.git
the idea of iterative benchmarking until elapsed
time is large enough is from the go testing
package, i'm not sure if this is the right
approach (for the malloc benchmarks it is not)
(makefile is uglier than it should be because i
still haven't fixed my musl-gcc)
finally: i added short int and int division
benchmarks to verify a discussion on irc :)
comments are welome
next reply other threads:[~2011-07-29 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 13:18 Szabolcs Nagy [this message]
2011-07-29 15:32 ` Solar Designer
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=20110729131839.GI29562@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).