From: Ian Lance Taylor <ian@cygnus.com>
To: vax@linkdead.paranoia.com
Cc: gas2@cygnus.com, baford@schirf.cs.utah.edu
Subject: Re: fixing i386 gas for 16-bit code
Date: Thu, 20 Jun 1996 08:46:00 -0000 [thread overview]
Message-ID: <199606201546.LAA05668@sanguine.cygnus.com> (raw)
In-Reply-To: <199606190541.AAA00489@linkdead.paranoia.com>
Date: Wed, 19 Jun 1996 00:41:40 -0500
From: VaX#n8 <vax@linkdead.paranoia.com>
I was wondering if you know how hard it would be (for me) to fix gas
to create 16-bit code properly, especially in the case of SIB (scaled
indexed based) addressing modes on the i386.
I don't know much about the i386 myself, so I'm CC'ing your note to
the gas developers list, gas2@cygnus.com. Perhaps somebody on the
list will have some useful information.
I have to hand code things like:
movb 1(%si), %dh
because it flubs the Mod-R/M byte.
Another cool thing would be 8-bit offset addressing. Coding all this by
hand is hair-pulling material. It is so ugly I chose not to do it :)
I used to hand code stuff when I was a kid, but it's pretty horrifying
to think that anybody still has to do it.
I believe that there are some 16 bit i386 assemblers out there.
Would I have to learn bfd? It confused the heck outta me when I looked
at the bfd source last time :-/
You shouldn't have to look at BFD for this sort of thing.
Ian
next parent reply other threads:[~1996-06-20 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199606190541.AAA00489@linkdead.paranoia.com>
1996-06-20 8:46 ` Ian Lance Taylor [this message]
1996-06-20 11:02 ` erich
1996-06-20 11:07 ` erich
1996-06-20 11:28 ` Bryan Ford
1996-06-20 12:16 ` Ian Lance Taylor
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=199606201546.LAA05668@sanguine.cygnus.com \
--to=ian@cygnus.com \
--cc=baford@schirf.cs.utah.edu \
--cc=gas2@cygnus.com \
--cc=vax@linkdead.paranoia.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).