public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Automatically optimizing hand coded assembler
Date: Fri, 18 Mar 2005 04:45:56 +0000	[thread overview]
Message-ID: <16954.23812.563464.146911@napali.hpl.hp.com> (raw)
In-Reply-To: <7848.1111113418@kao2.melbourne.sgi.com>

>>>>> On Fri, 18 Mar 2005 13:36:58 +1100, Keith Owens <kaos@sgi.com> said:

  Keith> The code in ia64_syscall_setup has several independent steps
  Keith> to execute.  Interleaving the instructions from each step by
  Keith> hand to avoid empty slots is painful, not to mention error
  Keith> prone.  Are there any tools available for this task?

  Keith> I envisage a tool where the user defines the instructions
  Keith> required for each step separately, including the stop bits
  Keith> needed for ordering within the individual step.  The
  Keith> resources used by each step must be disjoint.  The user also
  Keith> defines sync points, where steps must start, end or join with
  Keith> other steps.  The tool draws the DAG from the sync points
  Keith> then runs down the DAG, picking instructions from each step
  Keith> to best fill the slots.  The output is all the instructions,
  Keith> nicely interleaved to give the minimum number of bundles.

I suggested a project along these lines to a few students a while ago
but unfortunately nothing came out of it.  IIRC, Intel at one point
had a "visual assembler" which was doing something similar, but it was
Windows only and I don't know what became of it.

	--david

  reply	other threads:[~2005-03-18  4:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  2:36 Automatically optimizing hand coded assembler Keith Owens
2005-03-18  4:45 ` David Mosberger [this message]
2005-03-18  4:51 ` Matt Chapman

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=16954.23812.563464.146911@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --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