From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Pereira Habkost Subject: gcc-8086 Date: Thu, 13 May 2004 12:06:34 -0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <20040513150634.GP13835@duckman.distro.conectiva> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="o99acAvKqrTZeiCU" Return-path: Content-Disposition: inline List-Id: To: linux-8086@vger.kernel.org --o99acAvKqrTZeiCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --o99acAvKqrTZeiCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAo476caRJ66w1lWgRAsEKAJ4pIRSVfuuHqOEZl00f11wg4ikgcQCdE7rn +/NvTl9I61+Bx8umr/DETkA= =FJw5 -----END PGP SIGNATURE----- --o99acAvKqrTZeiCU--