From: artk@congruent.com (Arthur Kreitman)
To: rms@gnu.ai.mit.edu
Cc: dj@stealth.ctron.com, hjl@nynexst.com, gas2@cygnus.com,
masaki@eie.minolta.co.jp, raeburn@cygnus.com
Subject: [masaki@eie.monolta.co.jp: GAS bug and etc]
Date: Fri, 11 Nov 1994 15:01:00 -0000 [thread overview]
Message-ID: <9411112245.AA17970@Congruent.COM> (raw)
In-Reply-To: <9411112227.AA21589@mole.gnu.ai.mit.edu>
> Date: Fri, 11 Nov 94 17:27:20 -0500
> From: rms@gnu.ai.mit.edu (Richard Stallman)
>
> The theory is that since gas must already support these 16-bit
> instructions for the i386 anyway, it should be trivial to tell it that
> the *default* size should be assumed different, so that it would
> produce code that assumed it was running in a 16-bit segment instead
> of a 32-bit segment.
>
> Well, if the theory holds true, this won't cost us much.
>
> Then, the only work that would need to be done
> is to produce dos-style OMF output, which is also used for some 32-bit
> systems.
>
> This isn't useful for the GNU system at all; it should have lower
> priority than work that does help the GNU project. That's crucial for
> people who would work either on this or on some other GNU work. I
> hope they'll make sure they are not spending substantial time on this.
I would also point out that if you're interested, as I am, in being
compatible with the Evil Empire (Microsoft), that the value of any omf
or sixteen bit work will be zero real soon.
next prev parent reply other threads:[~1994-11-11 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-11 6:11 DJ Delorie
1994-11-11 6:28 ` H.J. Lu
1994-11-11 6:37 ` DJ Delorie
1994-11-11 6:45 ` H.J. Lu
1994-11-11 6:49 ` DJ Delorie
1994-11-11 7:06 ` H.J. Lu
1994-11-11 10:31 ` Richard Stallman
1994-11-11 10:46 ` DJ Delorie
1994-11-11 14:27 ` Richard Stallman
1994-11-11 15:01 ` Arthur Kreitman [this message]
1994-11-11 13:42 mycroft
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=9411112245.AA17970@Congruent.COM \
--to=artk@congruent.com \
--cc=dj@stealth.ctron.com \
--cc=gas2@cygnus.com \
--cc=hjl@nynexst.com \
--cc=masaki@eie.minolta.co.jp \
--cc=raeburn@cygnus.com \
--cc=rms@gnu.ai.mit.edu \
/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).