From mboxrd@z Thu Jan 1 00:00:00 1970 From: MFLD Subject: Re: We have a whole new ton of goodies to investigate... Date: Thu, 16 Apr 2015 09:35:34 +0200 Message-ID: <552F6646.9060703@gmail.com> References: <20150403214017.2e62b257@www.etchedpixels.co.uk> <552E9B6D.5020908@gmail.com> <20150415224107.69e71308@www.etchedpixels.co.uk> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VyyL5uDV+OeZu/vU8LWE+uLcewaxiMOP+cE7HyAKZRE=; b=iQtCLI58la3BGI5qMCCyoMrvSixfBmtxhDpzjuqFz36zFT/Si1tlHHig5Z3Z2Bmnb1 r2kkgK14wdQyEtU3uXTzZYqKXMmPwJwRqVMZXWPskfGszV/NdpQZPTH/RKqVJv7qDCmO hQSeUcOS76Q0vBaORTR03OawWpdKHuJHRXUuRJAVxSVz7B7tcmK1yd6rxocQibwvrX+m qhMj/89s4dBUZpLT2u3tv+TKAVPmaDJo87ZohCX7WaJNeo6tgoyXj0sT+AXtFtd2R666 9tX4YwC7KL/SvxzJFYU6mNSPC8nPL7fPhSAcnByulg0W48uqZfVXqIYHOTGYrndCFdnz YZvw== In-Reply-To: <20150415224107.69e71308@www.etchedpixels.co.uk> Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: Alan Cox Cc: ELKS Hello, Thanks for the interesting info about various toolchains for Fuzix. I=20 wonder why you include x86_16 target in the Fuzix challenge, as ELKS is= =20 already playing on that ground, but that is your baby, so... Back to ELKS : from what I see in the Coherent tree ('duff' was my=20 friend to have a more clear view), CC and AS386 output object files in=20 COFF, not A.OUT as BCC and AS86, so we would have to migrate to the=20 associated LD386, and update other tools as DIS88 (and the upcoming=20 MON86 and EMU86, scoop!). And despite that move, staying out of the=20 mainsteam on an unmaintained toolchain... I am afraid it would be a too heavy workload just to have fun with old=20 hardware or for learning purpose. I would instead spend my spare time i= n=20 splitting the recursive parser / code generator in BCC to keep it=20 simple, easy understandable and more maintainable (BCC =3D Basic C=20 Compiler for Beginner ?), following the PCC design without portability=20 in mind, and to be able to improve the register allocator without=20 dealing with any generic register representation as in GCC. The latest because I see Juan or Jody saving few bytes with big effort,= =20 while many bytes could be saved at the root by optimizing register usag= e=20 in function bodies (starting with the SI / DI push / pop for nothing);=20 and because I am already breaking the 64K segment limit with a first=20 draft of an Ethernet driver for my board. ANSI non-compliance is not=20 really a concern at that stage. But I could understand my rational is=20 only valid for my specific use case... Regards, MFLD Le 15/04/2015 23:41, Alan Cox a =E9crit : > Started to have a look to that huge stuff (not really sorted...), but > could you please explain the idea you have in mind ? Is this a sugges= t > to replace the DEV86 toolchain by something else ? > >At least the compiler. The Coherent compiler is an ANSI C compiler w= ith a > reasonably good optimiser on it. The tree seems to have versions for > 8086, 80286 (protected mode included) and 80386 (which is probably no= t > useful) > > >8086 I did a test build of the core with bcc, but would probably use= =20 > the coherent compiler eventually if it did 8086. Not sure there is=20 > that much point doing 8086, fixing the dumber bits ELKS inherited fro= m=20 > 32bit Linux would probably shrink it down to the point the size chang= e=20 > wasn't that big a deal. Alan=20 -- To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html