Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Chris Cummins <christopher.e.cummins@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] assembler: Add a regions visualizer tool
Date: Mon, 18 Mar 2013 16:04:42 +0000	[thread overview]
Message-ID: <20130318160441.GA3390@dyon.amr.corp.intel.com> (raw)
In-Reply-To: <1363110781-27837-1-git-send-email-christopher.e.cummins@intel.com>

On Tue, Mar 12, 2013 at 05:53:01PM +0000, Chris Cummins wrote:
> This adds a html/js tool for visualizing GEN instruction source operand
> regions, similar to those used in the Programmer's Reference Manual. To
> use the tool, open the file assembler/gen_regions/gen_regions.html in
> your browser-of-preference.

To give more details about that work, there's nothing better than
examples, visualizing regions taken directly from the published IVB
documentation:

http://damien.lespiau.name/intel/gen_regions.html#execsize=16&region=g4.2<16;8,2>w&advanced=0

http://damien.lespiau.name/intel/gen_regions.html#execsize=16&region=r5.0<1;8,2>:w&advanced=0

A quick review trying to use the tool:

  * I think it'd be better if byte 0 is at the right, it seems to be the
    usual ways to represent registers, lower bits at the right.
  * there's a bug when giving advanced=1 on the URL, the tool doesn't
    seem to take it into account
  * it'd be nice to get rid of the trailing white space (no review would
    be complete without a mention to trailing white space, rule #1 of
    the open source world) from the imported js files, I usually use a
    script around:
    	sed -i -e 's,[ \t]*$,,' $file

-- 
Damien

  reply	other threads:[~2013-03-18 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 17:53 [PATCH] assembler: Add a regions visualizer tool Chris Cummins
2013-03-18 16:04 ` Damien Lespiau [this message]
2013-03-19 10:49   ` Chris Cummins

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=20130318160441.GA3390@dyon.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=christopher.e.cummins@intel.com \
    --cc=intel-gfx@lists.freedesktop.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