From: Markus Dittrich <markusle@gentoo.org>
To: "Adam Piątyszek" <ediap@ET.PUT.Poznan.PL>
Cc: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] Re: [Fwd: Re: [atlas-devel] 1) ATLAS shared libraries; 2) "ASM" -> "ASM VOLATILE"]
Date: Fri, 25 Aug 2006 12:42:08 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.64.0608251229580.6200@woodpecker.gentoo.org> (raw)
In-Reply-To: <44EE9E48.5090801@et.put.poznan.pl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 25 Aug 2006, Adam Pityszek wrote:
> Dear Markus, gentoo-science guys,
>
> Please find below the reply from Clint to my yesterday's email related to
> our work on ATLAS shared libraries in Gentoo.
>
> Markus, I think we can help with answering the questions (2) and (3). Of
> course, volunteers from gentoo-science are welcome as well.
>
> BR,
> /ediap
>
> (1) Is it true that the extra pointer may still be used if we restore it at
> end of assembly routine?
> (2) Does throwing the -fpic or other required compiler flag changes change
> the best cases (thus necessitating doubling the arch defaults)?
> (3) What is the overall performance affect when using .so?
>
> I've tried to answer (1) by looking at some docs, but never got convinced
> either way. I've been meaning to write a resister stress-test to see if
> I can make gcc use the reserved register in a function w/o global data.
> Perhaps you know?
>
> You guys could help with (2) & (3) if you like. You could build out-of-box
> to .a on whatever machines you can, and then build it to .so using your
> gentoo harness, and post some head-to-head timings . . . If, as we suspect,
> the difference is essentially zero, that makes .so a lot more attractive . . .
>
Hi Adam,
Thanks for talking to upstream about this and Clint's response
sounds encouraging. We could definitely help out with 2) and 3);
it would be good to know anyway how well we do with our shared
libs. In doing so we should also test the impact of using
the 387 floating point unit versus the sse instruction set.
According to Clint, the former can give a significant performance
gain on some CPU's. If that is the case it might be worth a
note in the ebuild to make our users aware of it.
We should get a hold of a nice benchmark suite for this purpose;
Clint has posted one on this gcc bug
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27827
which we might be able to use. I'll have a look at it.
Best,
Markus
- --
Markus Dittrich (markusle)
Gentoo Linux Developer
Scientific applications
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE7vAixlRwCwb7k40RAu4HAJ9qZ9UZr5Nt6rTAC/XoTXezJ+yqswCdE9iF
9766l1jX9prxDzgSjnsWPWU=
=++uN
-----END PGP SIGNATURE-----
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-25 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 6:52 [gentoo-science] [Fwd: Re: [atlas-devel] 1) ATLAS shared libraries; 2) "ASM" -> "ASM VOLATILE"] Adam Piątyszek
2006-08-25 12:42 ` Markus Dittrich [this message]
2006-08-25 14:23 ` [gentoo-science] " M. Edward (Ed) Borasky
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=Pine.LNX.4.64.0608251229580.6200@woodpecker.gentoo.org \
--to=markusle@gentoo.org \
--cc=ediap@ET.PUT.Poznan.PL \
--cc=gentoo-science@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox