Linked by Thom Holwerda on Wed 9th Nov 2011 21:26 UTC, submitted by edwin
General Unix Way back in 2002, MIT decided it needed to start teaching a course in operating system engineering. As part of this course, students would write an exokernel on x86, using Sixth Edition Unix (V6) and John Lions' commentary as course material. This, however, posed problems.
Thread beginning with comment 497036
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: binary for windows....
by Vanders on Sat 12th Nov 2011 14:09 UTC in reply to "RE[6]: binary for windows.... "
Vanders
Member since:
2005-07-06

Theoretically, using static binaries, an optimizing compiler could analyze the call paths and eliminate all the glue code.


I can't help but feel that the time and effort needed to do that well would be significant, yet only save a tiny fraction of the load and link time for a binary that uses classic shared libraries.

Reply Parent Score: 2

Alfman Member since:
2011-01-28

Vanders,

"I can't help but feel that the time and effort needed to do that well would be significant, yet only save a tiny fraction of the load and link time for a binary that uses classic shared libraries."

I actually think that a sequential read of a (possibly larger) static binary on disk could be much faster than many fragmented reads from many shared libraries.

I agree that this would not be worthwhile to change under linux, which is already heavily invested in it's current implementation. However I think there is merit in considering alternate methodologies for new platforms.

Reply Parent Score: 2