From mboxrd@z Thu Jan 1 00:00:00 1970 From: sandeep Subject: Re: Compilers Date: Fri, 28 May 2004 20:14:03 +0530 Sender: linux-8086-owner@vger.kernel.org Message-ID: <40B75033.3060302@codito.com> References: <200405281142.38116.dg@cowlark.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200405281142.38116.dg@cowlark.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-8086@vger.kernel.org > Given that currently the ELKS kernel is about 70kB of code, a little > problematic given the 64kB limit, anything that will make the code smaller is Apart from using ways/tools to get smaller code to fit it 64KB, I guess couple of other options should also be possible. If you see elks features wish-list, with more wishes fulfilled it might not be possible to have it fit in 64KB, may be unless entire OS is handcoded in assembly and tweaks/hacks applied here and there as needed to produce mainly smaller (faster) code. 1. something like loadable modules / overlays that can help here. these overlays needn't be overlays in dos .OVL file ways but part of executable, and executable header gives information about these. yeah it will require sllightly different/ modified executable format to be devised. 2. even if code and data for elks kernel is more than 64 KB, that will not be a problem if this code and data is not moved around b/w memory and disk, i.e. once loaded it stays there till reboot. within kernel code you can even have far pointers stored even as local variables. -- regards sandeep -------------------------------------------------------------------------- Loose bits sink chips. --------------------------------------------------------------------------