From: Richard Stallman <rms@santafe.edu>
To: robertl@dgii.com
Cc: gas2@cygnus.com
Subject: Re: other apps that assemble code
Date: Thu, 05 Feb 1998 23:26:00 -0000 [thread overview]
Message-ID: <199802060722.AAA25002@wijiji.santafe.edu> (raw)
In-Reply-To: <19980205123732.35907@dgii.com>
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.
I made a basic design decision long ago not to try to do anything like
this. The reason is that it involves pushing most of the compiler and
linker down into the assembler. That contorts the design and makes a
lot of extra work, and it just isn't worth that much trouble.
next prev parent reply other threads:[~1998-02-05 23:26 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 [this message]
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=199802060722.AAA25002@wijiji.santafe.edu \
--to=rms@santafe.edu \
--cc=gas2@cygnus.com \
--cc=robertl@dgii.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).