From: sandeep <sandeep@codito.com>
To: linux-8086@vger.kernel.org
Subject: Re: Compilers
Date: Fri, 28 May 2004 20:14:03 +0530 [thread overview]
Message-ID: <40B75033.3060302@codito.com> (raw)
In-Reply-To: <200405281142.38116.dg@cowlark.com>
> 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.
--------------------------------------------------------------------------
next prev parent reply other threads:[~2004-05-28 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 10:42 Compilers David Given
2004-05-28 14:44 ` sandeep [this message]
2004-05-28 14:47 ` Compilers Eduardo Pereira Habkost
2004-05-29 11:42 ` Compilers Mark Junker
2004-05-29 11:58 ` Compilers David Given
2004-05-29 12:32 ` Compilers Mark Junker
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=40B75033.3060302@codito.com \
--to=sandeep@codito.com \
--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