From: hjl@nynexst.com (H.J. Lu)
To: baford@schirf.cs.utah.edu (Bryan Ford)
Cc: gas2@cygnus.com, raeburn@cygnus.com (Ken Raeburn),
ian@cygnus.com (Ian Lance Taylor)
Subject: Re: 16-bit i386 code support in GAS
Date: Wed, 09 Nov 1994 07:20:00 -0000 [thread overview]
Message-ID: <9411091519.AA29119@titanic.nynexst.com> (raw)
In-Reply-To: <199411091455.HAA25021@schirf.cs.utah.edu>
>
> (Sorry if this isn't the right place to ask this question;
> I couldn't find any better address in the GAS documentation...)
>
> How difficult would it be to add a feature to the i386 version
> of GAS to allow it to generate 16-bit i386 code? It seems like
> it should be a trivial change - just add a directive that inverts
> the decision of whether or not to add size prefixes to each
> instruction, right? Such a feature would make it possible to
> avoid the icky old inverted-syntax, non-cross-compiling as86 and
> ld86 programs for writing boot-related code in Mach (Hurd/Lites)
> and Linux.
>
> So, could someone either add this feature, or point me to the
> right parts of gas-i386 so I can do it myself, or tell me why
> it isn't so simple?
>
Please take a look at my CC field.
--
H.J. Lu
NYNEX Science and Technology, Inc. hjl@nynexst.com
next parent reply other threads:[~1994-11-09 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199411091455.HAA25021@schirf.cs.utah.edu>
1994-11-09 7:20 ` H.J. Lu [this message]
1994-11-09 10:49 ` Ken Raeburn
1994-11-09 11:06 ` Bryan Ford
1994-11-09 23:35 ` Ken Raeburn
1994-11-10 6:57 ` Bryan Ford
1994-11-10 11:51 ` Ken Raeburn
1994-11-09 19:22 ` Rick Sladkey
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=9411091519.AA29119@titanic.nynexst.com \
--to=hjl@nynexst.com \
--cc=baford@schirf.cs.utah.edu \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.com \
--cc=raeburn@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).