From: Maciej Hrebien <m_hrebien@wp.pl>
To: linux-assembly@vger.kernel.org
Subject: SIMD question
Date: Wed, 22 Feb 2006 19:20:20 +0100 [thread overview]
Message-ID: <43FCAB64.5090406@wp.pl> (raw)
Hello everybody!
I have quite big commercial software and the producer tells me that they
did heavy SIMD optimisations to get maximum speed in solving a given
problem. Of course i don't have the source code but the soft runs in
GNU/Linux enviroment (x86 architecture).
I did some experiments on smaller problems and i suspect that this
procuder's SIMD optimisations is a one big lie - the code can run much
faster. There are some SIMD instructions when i disassemble this
~250-meg binaries but analysing it is a quite frustrating job.
My question is: is there a way (without touching the kernel as yet) to
trace in a given period of time the CPU so that i will be noticed when
SIMD instructions are being executed? Or maybe setting debugging traps
in all SIMD occuring places is the only way?
PS Thanks to Konstantin we have new asmutils :) Feel free, you - the
reader of this message, to improve my parts of code which were written
many many days ago so even beautifullization is warmly welcome ;)
Best regards,
Maciek
reply other threads:[~2006-02-22 18:20 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=43FCAB64.5090406@wp.pl \
--to=m_hrebien@wp.pl \
--cc=linux-assembly@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).