public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Testing the performance of instruction Scheduler
@ 2000-11-02 21:11 phani narasimhan venkata sesha myreddy
  0 siblings, 0 replies; only message in thread
From: phani narasimhan venkata sesha myreddy @ 2000-11-02 21:11 UTC (permalink / raw)
  To: gcc-help

hai all,
How do i test the performance of instruction scheduler.
I have written an instruction scheduler for a database code generator.
The scheduler is simple and tuned to the graph generated, as i get
some class of graphs. It contains the global, local scheduler and the
instruciton grouping logic.

I wonder i did not got the expected performance. The gain for some
graphs
is 6 to 8 %. The worst part is the performance goes down for some
graphs.
The graph size is very huge. some times 200 blocks and 2000
instructions.
The instructions generated is very optimal.

I read the ultrasparc-II manual and in it the instructions are properly
scheduled
it is possible to bring CPI as low as 0.25. I am not able to visualise
this much percentage gain overall.

Is there any tool to calculate the number of cycles taken by the code
at run-time?

Is there any tool to find for a specific run how many data cache misses
have
occured?

Is there any tool that give the number of pieline stalls that occured ?

Is there any other way to project the performance apart from just
comparing the
execution times?

How much performance gain in terms of percentage one can expect from an
instruction scheduler?

Hoping a detailed early reply.

Thanks.
sincierly,
phani.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2000-11-02 21:11 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-11-02 21:11 Testing the performance of instruction Scheduler phani narasimhan venkata sesha myreddy

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 read-only IMAP folder(s) and NNTP newsgroup(s).