From: Andrey Romanenko <bigral@i.com.ua>
Cc: linux-8086@vger.kernel.org
Subject: Re: EDE - Personal Suggestions and Ideas
Date: Fri, 28 May 2004 14:23:50 +0300 [thread overview]
Message-ID: <40B72146.4080202@i.com.ua> (raw)
In-Reply-To: <200405281111.50735.dg@cowlark.com>
David Given wrote:
>But if you're not programming in C, you don't have this limitation. Unix
>traditionally is programmed in C, so people don't think about this much, but
>it would be really nice if the kernel would manage all the segment registers
>and not just CS and DS. So that, if you like, you could load a binary that
>allocated all four segments. This would allow nice features such as a Basic
>interpreter that stored its byte-code in ES, its working stack in SS, and
>used DS for workspace.
>
>
You propose to maintain two or more pointers that points to same memory
location but to different areas that may cross over.
That means that if you have (pointer == pointer2) it is not enough to
say that they are poining to the same object.
I think this situation is COMPLETE NIGHTMARE that gives us no value but
only troubles.
Yes I understand that 8086 architecture alredy support it but this is
not a reason to bring this to C compiler.
I belive C programmer does not need to know about all this 8086's
xxxx:xxxx memory structure at all.
It is job of compiler to convert 32bit pointers to xxxx:xxxx addresses.
So ideally there would be two types of executables: old
(that we have now) and new with multi segments where compiler using
kernel manages all segments allocation and converts
32bit pointers to apropriate locations.
Andrey
next prev parent reply other threads:[~2004-05-28 11:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 14:23 [Fwd: Re: EDE - Personal Suggestions and Ideas] Miguel Bolanos
2004-05-25 17:10 ` David Given
2004-05-26 6:20 ` AW: " Mario Premke
2004-05-26 10:09 ` David Given
2004-05-26 10:30 ` Gábor Lénárt
2004-05-26 11:43 ` AW: " Mario Premke
2004-05-26 11:57 ` Gábor Lénárt
2004-05-26 12:39 ` AW: " Mario Premke
2004-05-26 13:06 ` Gábor Lénárt
2004-05-26 14:17 ` David Given
2004-05-26 15:10 ` Gábor Lénárt
2004-05-26 16:00 ` Andrey Romanenko
2004-05-26 16:49 ` David Given
2004-05-26 17:19 ` Eduardo Pereira Habkost
2004-05-27 9:09 ` Gábor Lénárt
2004-05-26 17:42 ` Andrey Romanenko
2004-05-26 23:19 ` David Given
2004-05-27 6:07 ` EDE - Personal Suggestions and Ideas sandeep
2004-05-27 15:51 ` Eduardo Pereira Habkost
2004-05-28 8:09 ` sandeep
2004-05-28 8:10 ` Gábor Lénárt
2004-05-28 10:11 ` David Given
2004-05-28 11:23 ` Andrey Romanenko [this message]
2004-05-28 12:14 ` David Given
2004-05-29 5:28 ` Dan Olson
2004-05-28 10:30 ` sandeep
2004-05-26 22:34 ` AW: [Fwd: Re: EDE - Personal Suggestions and Ideas] Harry Kalogirou
2004-05-27 9:00 ` Gábor Lénárt
2004-05-27 6:04 ` Dan Olson
2004-05-27 7:14 ` Andrey Romanenko
2004-05-27 9:32 ` David Given
2004-05-27 10:19 ` Gábor Lénárt
2004-05-27 21:07 ` Tommy McCabe
2004-05-28 7:39 ` Gábor Lénárt
2004-06-01 13:46 ` Gabucino
2004-06-02 9:03 ` AW: [Fwd: Re: EDE - Personal Suggestions and Ideas][OT] Javier Sedano
2004-05-26 11:34 ` AW: AW: [Fwd: Re: EDE - Personal Suggestions and Ideas] Mario Premke
2004-05-26 12:09 ` Gábor Lénárt
2004-05-27 5:56 ` Dan Olson
2004-05-26 22:42 ` Harry Kalogirou
-- strict thread matches above, loose matches on Subject: below --
2004-05-25 13:33 EDE - Personal Suggestions and Ideas Miguel Bolanos
2004-05-26 10:06 ` Gábor Lénárt
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=40B72146.4080202@i.com.ua \
--to=bigral@i.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