Linked by Thom Holwerda on Thu 26th Mar 2009 23:34 UTC
Thread beginning with comment 355682
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2005-11-19
I have no clue what you mean by a LLVM as an OS. That is not the target of LLVMs at all...
My idea is to use LLVM as an installer and packager for libraries and applications. Most of AmigaOS fits into one of those categories. All that would be needed is for enough OS to boot the LLVM command line version of llc to allow the bitcode files representing some of the higher-level functionality of AmigaOS to be installed as a thin binary.
The only time you'd need proprietary binary codes is to access the BIOS/Kickstart/UBoot-level functionality and the filesystem required to install the supporting OS functions that are required to load the llc command. This would include HD-Toolbox and the CD-ROM and hard-disk FFS2 filesystems, Dos.library, and the Exec.library kernal. Since most of the libraries in LLVM compile statically into the llc command, there would be most of the operating system that could be made at install time into the hard disk from bitcode.