Update Home
parent
631b369940
commit
ffeb553c4e
4
Home.md
4
Home.md
@ -15,7 +15,9 @@ To safeguard against dependency hell, all the essential software needed to devel
|
||||
* GCC - GPL, Clang - Apache licenses
|
||||
* While the standard may move to LLVM, GCC still remains the industry standard as of now.
|
||||
|
||||
Decision: They have many differences, above are the potentially most relevant. The GPL license seems preferable in this case, which is a point in favor of GCC. A major performance consideration comes when there are a lot of lib files as well as `-debug` mode (which is expected to be the case in this project). This difference will come down to the linker, and seeing as `lld` can be a drop-in replacement for `ld`, and added independently of Clang, it is not a major point in favor of Clang. We can simply install `lld` from the LLVM backend (Clang is just the frontend), and pass the `-fuse-ld=lld` flag to GCC to make it use `lld` instead of `ld`. For these reasons, I propose to start with GCC.
|
||||
Decision: TL;DR - *GCC*.
|
||||
|
||||
They have many differences, above are the potentially most relevant. The GPL license seems preferable in this case, which is a point in favor of GCC. A major performance consideration comes when there are a lot of lib files as well as `-debug` mode (which is expected to be the case in this project). This difference will come down to the linker, and seeing as `lld` can be a drop-in replacement for `ld`, and added independently of Clang, it is not a major point in favor of Clang. We can simply install `lld` from the LLVM backend (Clang is just the frontend), and pass the `-fuse-ld=lld` flag to GCC to make it use `lld` instead of `ld`. For these reasons, I propose to start with GCC.
|
||||
|
||||
Preliminary list of essential software:
|
||||
- QEMU: open-source machine emulator
|
||||
|
Loading…
Reference in New Issue
Block a user