public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <devans@cygnus.com>
To: richard.earnshaw@arm.com
Cc: gas2@cygnus.com
Subject: Re: other apps that assemble code
Date: Thu, 05 Feb 1998 09:49:00 -0000	[thread overview]
Message-ID: <199802051748.JAA28227@canuck.cygnus.com.> (raw)
In-Reply-To: <199802051741.RAA14888@sun52.NIS.cambridge>

   Date: Thu, 05 Feb 1998 17:41:27 +0000
   From: Richard Earnshaw <rearnsha@arm.com>

   > Can anyone think of any useful applications that want to
   > assemble code besides an assembler?
   > 
   > A debugging session?
   > [I can see perhaps only a minor usefulness here, but maybe there are
   > cases where it's really useful, and maybe there are other examples.]

   How about a compiler.  It doesn't have to spit out assembly language 
   directly, and might be able to do a better job in some cases if it could 
   write an object file directly.

Yes, but in this case does the compiler internally create assembly code
and then parse that assembly code to spit out the object file?
Maybe there is a compiler that does so, but I would think it would just
keep the insns internally in some form and not deal with assembly code at all.

   (or am I missing your point?)

I'm not sure but I think so.

  reply	other threads:[~1998-02-05  9: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
1998-02-05 11:09           ` Doug Evans
1998-02-05  9:43 ` Richard Earnshaw
1998-02-05  9:49   ` Doug Evans [this message]
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=199802051748.JAA28227@canuck.cygnus.com. \
    --to=devans@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=richard.earnshaw@arm.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).