From: Konstantinos Margaritis <markos@codex.gr>
To: linuxppc-dev@ozlabs.org
Subject: libfreevec benchmarks
Date: Thu, 21 Aug 2008 19:09:15 +0300 [thread overview]
Message-ID: <200808211909.16852.markos@codex.gr> (raw)
Benh suggested that I made this more known, and in particular to this list, so
I send this mail in hope that some people might be interested. In particular,
I ran the following benchmarks against libfreevec/glibc:
http://www.freevec.org/content/libfreevec_104_benchmarks_updated
libfreevec has reached a very stable point, where me and a couple of others
(the OpenSuse PowerPC port developer being one) have been using it for weeks
(personally I've been using it for months), using the LD_PRELOAD mechanism (as
explained here:
http://www.freevec.org/content/howto_using_libfreevec_using_ld_preload).
The OpenSuse guys even consider using it by default on the ppc port even, but
that's not final of course.
glibc integration _might_ happen if glibc developers change their attitude (my
mails have been mostly ignored).
Last, I've also been working on a libm rewrite, though this will take some
time still. I've reimplemented most math functions at the algorithm level, eg.
so far, most functions achieve 50%-200% speed increase at full IEEE754
accuracy (mathematically proven, soon to be published online) without using
Altivec yet, just by choosing a different approximation method (Taylor
approximation is pretty dumb if you ask me anyway).
Regards
Konstantinos Margaritis
Codex
http://www.codex.gr
next reply other threads:[~2008-08-21 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 16:09 Konstantinos Margaritis [this message]
2008-08-22 17:44 ` libfreevec benchmarks Ryan S. Arnold
2008-08-22 17:50 ` Ryan S. Arnold
2008-08-24 8:03 ` Konstantinos Margaritis
2008-09-02 22:24 ` Ryan S. Arnold
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=200808211909.16852.markos@codex.gr \
--to=markos@codex.gr \
--cc=linuxppc-dev@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.