From: Joel Sherrill <joel@OARcorp.com>
To: Doug Evans <devans@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: other apps that assemble code
Date: Thu, 05 Feb 1998 10:49:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980205124505.25442H-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199802051756.JAA28237@canuck.cygnus.com.>
On Thu, 5 Feb 1998, Doug Evans wrote:
> Date: Thu, 5 Feb 1998 11:47:36 -0600 (CST)
> From: Joel Sherrill <joel@OARcorp.com>
>
> I have seen articles about "optimizing assemblers" for really smart cpus
> which insert nops, reorder instructions to avoid stalls, reassign
> registers, etc. This type of tools would benefit from a generic assembly
> language parser.
>
> Ok, but methinks this is still just GAS.
> Or am I misunderstanding something?
I guess it could be but would it be cleaner to have it as a separate tool
which manipulated source. Technically either approach is viable.
From an implementation standpoint, having a separate tool might make that
tool easier to update/port. From a strict viewpoint, gas shoud only take
assembler and generate object. That is a difficult enough process as it
is. Having to deal with possible code reordering, nops could only make
gas more complex and difficult to maintain.
I don't know much about gas internals. Does it have an internal
representation which could be manipulated like this?
-joel
next prev parent reply other threads:[~1998-02-05 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-05 9:04 Doug Evans
1998-02-05 9:26 ` Joel Sherrill
1998-02-05 9:37 ` Doug Evans
1998-02-05 9:47 ` Joel Sherrill
1998-02-05 9:57 ` Doug Evans
1998-02-05 10:38 ` Robert Lipe
1998-02-05 23:26 ` Richard Stallman
1998-02-05 10:49 ` Joel Sherrill [this message]
1998-02-05 11:09 ` Doug Evans
1998-02-05 9:43 ` Richard Earnshaw
1998-02-05 9:49 ` Doug Evans
1998-02-05 10:35 ` Nick Clifton
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=Pine.BSF.3.96.980205124505.25442H-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=devans@cygnus.com \
--cc=gas2@cygnus.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).