From: Robert Lipe <robertl@dgii.com>
To: gas2@cygnus.com
Subject: Re: other apps that assemble code
Date: Thu, 05 Feb 1998 10:38:00 -0000 [thread overview]
Message-ID: <19980205123732.35907@dgii.com> (raw)
In-Reply-To: <199802051756.JAA28237@canuck.cygnus.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
>
> Ok, but methinks this is still just GAS.
> Or am I misunderstanding something?
I'm not sure if it really goes to answer the original question or not,
but there exist highly optimizing assemblers. The one I worked with was
the MIPS assembler. I don't know if that technology was kept when MIPS
collapsed into SGI or not. By that time, I'd defected from that train.
The mips uopt pass did many of the same optimizations at the assembler
level that GCC does a couple of levels up. It did flow analysis,
constant propogation, branch prediction and all sort os wild and crazy
things. The "optimization" in GAS is far less ambitious.
This is the lone thing that I actually miss about the MIPS tools.
--
Robert Lipe http://www.dgii.com/people/robertl robertl@dgii.com
next prev parent reply other threads:[~1998-02-05 10:38 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 [this message]
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=19980205123732.35907@dgii.com \
--to=robertl@dgii.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).