From: Bryan Ford <baford@schirf.cs.utah.edu>
To: Ken Raeburn <raeburn@cygnus.com>
Cc: gas2@cygnus.com
Subject: Re: 16-bit i386 code support in GAS
Date: Wed, 09 Nov 1994 11:06:00 -0000 [thread overview]
Message-ID: <199411091906.MAA25430@schirf.cs.utah.edu> (raw)
In-Reply-To: <9411091849.AA00797@cujo.cygnus.com>
> > (Sorry if this isn't the right place to ask this question;
> > I couldn't find any better address in the GAS documentation...)
>
>Probably bug-gnu-utils is the best publicly advertised place. The gas2
>list at Cygnus is a less advertised one, intended mainly for developers.
I've sent messages (including bug _fixes_, not just reports)
to bug-gnu-utils several times before, and have never gotten any
kind of response whatsoever - my mail just disappears into the void. :-)
>[...16 bit support...]
>I'd like to see this work done (but cleanly!), for precisely the reasons
>you mention. Anyone doing kernel or stand-alone program development
>currently has to have as86 and ld86 as well as the GNU tools for the
>32-bit code. That's just silly.
>
>I'd also like to have a general overhaul of the i386 back end done. It's
>got lots of other problems, especially some dealing with segment
>registers. I've been thinking about doing some of this work myself, but
>if you've got a strong overall understanding of the quirks of the i386
>instruction set, and a lot of spare time you want to donate, let me
>know...
I have a pretty good understanding of the 386 instruction set,
but no experience in the GAS source code, and practically no free time.
I was thinking of adding the 16-bit support myself if it was fairly trivial,
but it sounds as if it isn't. I still might be able to, but not any time soon...
Thanks...
Bryan
next prev parent reply other threads:[~1994-11-09 11:06 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
1994-11-09 10:49 ` Ken Raeburn
1994-11-09 11:06 ` Bryan Ford [this message]
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=199411091906.MAA25430@schirf.cs.utah.edu \
--to=baford@schirf.cs.utah.edu \
--cc=gas2@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).