From: Andrey Romanenko <Andrey.Romanenko@infopulse.com.ua>
To: Andrey Romanenko <Andrey.Romanenko@infopulse.com.ua>
Cc: "linux-8086@vger.kernel.org" <linux-8086@vger.kernel.org>
Subject: RE: Kernel size over 64K: what is needed, how to implement?
Date: Wed, 22 Feb 2012 14:53:15 +0000 [thread overview]
Message-ID: <FC79A7424F669341A72EFA787A3C767541F9005A@exchdb1-vm-srv.infopulse.local> (raw)
In-Reply-To: <FC79A7424F669341A72EFA787A3C767541F8ECD7@exchdb1-vm-srv.infopulse.local>
>We could take on look on GCC port for 8086, you could find more
>information about it on this mailing list archive. In fact those GCC
>patch for 8086 were applied to GCC mainline, but few time after that
>they were removed.
Hello, I think GCC is the compiler targeted to bigger systems where no problem with memory limit exist.
(there are very similar difference between ELKS and real Linux kernel, ELKS designed with 64kb limit in mind.) We could consider to use SDCC instead, btw from now on SDCC support "named address space"
http://sdcc.sourceforge.net/doc/sdccman.html/node64.html
this feature potentially may add multi data segments executables to ELKS.
Also, It seems to me that all those systems supported by SDCC are very similar to 8088 computer because of their 64kb address space limit.
thanks,
Andrey
prev parent reply other threads:[~2012-02-22 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 18:20 Kernel size over 64K: what is needed, how to implement? Jody Bruchon
2012-02-17 22:51 ` David Given
2012-02-19 21:36 ` David Given
2012-02-19 23:01 ` Kirn Gill
2012-02-20 0:51 ` David Given
2012-02-20 13:13 ` Alan Carvalho de Assis
2012-02-21 18:24 ` Juan Perez-Sanchez
2012-02-22 0:31 ` David Given
[not found] ` <FC79A7424F669341A72EFA787A3C767541F8ECD7@exchdb1-vm-srv.infopulse.local>
2012-02-22 14:53 ` Andrey Romanenko [this message]
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=FC79A7424F669341A72EFA787A3C767541F9005A@exchdb1-vm-srv.infopulse.local \
--to=andrey.romanenko@infopulse.com.ua \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).