public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@tuliptree.org>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 dispersal analysis capability
Date: Wed, 21 Sep 2005 21:47:40 +0000	[thread overview]
Message-ID: <1127339260.26485.57.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <20050921182143.GA30873@sgi.com>

On Wed, 2005-09-21 at 11:23, Jack Steiner wrote:
> In 2002, Gary Hade posted a patch to binutils that added dispersal
> analysis to the output of objdump. Does anyone know what happened to
> the patch? Is there another tool that provides the same information?

As for the "other tool" part of this question, you can get some info
from gcc by using -fsched-verbose=2 -fdump-rtl-sched1 -fdump-rtl-mach.
This will give you a lot of info about what the gcc instruction
scheduler did, but the interesting stuff is in the  "--> " lines in the
*.mach file.  This will give you lines like
;;        1--> 11   r14=[r14]                          :2_M_only_um01
which gives you the cycle number (1), the gcc internal instruction
number (11), an abstract representation of what the instruction does
(r14=[r14]), and the scheduling unit info (2_M_only_um01).  The 2 stands
for Itanium2.  The M stands for a memory unit.  The only_um01 means it
must be scheduled to one of the first two memory units.

This info is to help gcc developers debug instruction scheduler related
problems, and isn't really meant to be easily readable by end users, but
you may find it useful.

Actually, the above command only works for gcc-4.  For gcc-3, just use
-fsched-verbose=2 -da and ignore the non-scheduler related dump files.



  parent reply	other threads:[~2005-09-21 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 18:23 ia64 dispersal analysis capability Jack Steiner
2005-09-21 18:31 ` Stephane Eranian
2005-09-21 20:23 ` Gary Hade
2005-09-21 21:30 ` James E Wilson
2005-09-21 21:47 ` James E Wilson [this message]
2005-09-22  5:45 ` David Mosberger-Tang
2005-09-22 16:58 ` Jack Steiner
2005-09-22 17:30 ` Gary Hade
2005-09-23 20:41 ` John S. Worley

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=1127339260.26485.57.camel@aretha.corp.specifix.com \
    --to=wilson@tuliptree.org \
    --cc=linux-ia64@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