public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
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 09:47:00 -0000	[thread overview]
Message-ID: <Pine.BSF.3.96.980205113948.25442G-100000@vespucci.advicom.net> (raw)
In-Reply-To: <199802051735.JAA28194@canuck.cygnus.com.>

On Thu, 5 Feb 1998, Doug Evans wrote:

>    Date: Thu, 5 Feb 1998 11:26:18 -0600 (CST)
>    From: Joel Sherrill <joel@OARcorp.com>
> 
>    Also people do write assembly language so not all input is compiler
>    generated. I know this almost qualifies as a smart mouthed suggestion. :)
> 
> When they do this, is the code ever fed through anything other than
> an assembler that takes in assembly files and spits out object files?
> 
> The reason I'm asking is that I have an assembly language parser
> for some chips and am wondering whether it has any use outside of GAS.

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.

Another possible use is an assembly translator which takes code for one
cpu and attempts to convert it to another assembly language.  I know this
sounds scary but on some of the early RTEMS ports (RTEMS was ~20% assembly
then), I used some sed and awk scripts to convert Motorola assembly to
Intel i386 and i960 assembly as a starting point.  A smart tool could save
you a lot of bloody fingers here.

I suspect that Hunter Ready Systems (remember the original VRTX) had an
inhouse product like this since they claimed the entire kernel was in
assembly.  I never could figure out how that would be practical to maintin
unless it was written in a "pseudo-assembly" and converted.

Just some ideas.

--joel


  reply	other threads:[~1998-02-05  9:47 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 [this message]
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
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.980205113948.25442G-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).