public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Pereira Habkost <ehabkost@conectiva.com.br>
To: linux-8086@vger.kernel.org
Subject: gcc-8086
Date: Thu, 13 May 2004 12:06:34 -0300	[thread overview]
Message-ID: <20040513150634.GP13835@duckman.distro.conectiva> (raw)

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

Hi, all,

I've been working on the DJ gcc i86 target patches, and I've been making
it work using gas instead of nasm, and had some progress.

I would like to know if there is anyone interested on the gcc-8086 work,
here, or that have worked on it before. I am starting to look at ELKS
code, and I plan to test their binaries using ELKS.

Another question: is there any interest from the ELKS project in using
GCC to build ELKS? Wouldn't it make easier the work of porting existing
Linux Kernel code to ELKS, for example?

I am wondering how painful would be making the actual Linux Kernel code
work on a 16-bit arch, once we have a working gcc-8086. The Linux code
seems to be "at-least-32-bit dependant" in many parts that are supposed
to be arch-independant. But once those parts are changed, there are some
strong reasons for not doing it?

--
Eduardo

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-05-13 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 15:06 Eduardo Pereira Habkost [this message]
2004-05-13 16:02 ` gcc-8086 Miguel Bolanos
2004-05-13 16:44   ` gcc-8086 Eduardo Pereira Habkost
2004-05-13 17:37     ` gcc-8086 Miguel Bolanos
2004-05-13 21:15     ` gcc-8086 patch (very experimental) Eduardo Pereira Habkost

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=20040513150634.GP13835@duckman.distro.conectiva \
    --to=ehabkost@conectiva.com.br \
    --cc=linux-8086@vger.kernel.org \
    /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