From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Automatically optimizing hand coded assembler
Date: Fri, 18 Mar 2005 02:36:58 +0000 [thread overview]
Message-ID: <7848.1111113418@kao2.melbourne.sgi.com> (raw)
The code in ia64_syscall_setup has several independent steps to
execute. Interleaving the instructions from each step by hand to avoid
empty slots is painful, not to mention error prone. Are there any
tools available for this task?
I envisage a tool where the user defines the instructions required for
each step separately, including the stop bits needed for ordering
within the individual step. The resources used by each step must be
disjoint. The user also defines sync points, where steps must start,
end or join with other steps. The tool draws the DAG from the sync
points then runs down the DAG, picking instructions from each step to
best fill the slots. The output is all the instructions, nicely
interleaved to give the minimum number of bundles.
next reply other threads:[~2005-03-18 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 2:36 Keith Owens [this message]
2005-03-18 4:45 ` Automatically optimizing hand coded assembler David Mosberger
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=7848.1111113418@kao2.melbourne.sgi.com \
--to=kaos@sgi.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