3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-28 04:24:26 +01:00
Code Issues Releases Wiki Activity

gcc project idea

Browse Source
This commit is contained in:
Ciro Santilli
2018-09-12 12:39:09 +01:00
parent 5e83660e86
commit d3f627d41e
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.adoc
View File

@@ -31,12 +31,12 @@ The current components we focus the most on are:
* full systems emulators, currently <<qemu-buildroot-setup,qemu>> and <<gem5-buildroot-setup,gem5>> * full systems emulators, currently <<qemu-buildroot-setup,qemu>> and <<gem5-buildroot-setup,gem5>>
* <<buildroot>>. We use and therefore document, a large part of its feature set. * <<buildroot>>. We use and therefore document, a large part of its feature set.
but this setup could be of great benefit for: The following components are not covered, but it shouldn't be hard to do:
* C standard libraries * C standard libraries
* compilers * compilers. Project idea: add a new instruction to x86, then hack up GCC to actually use it, and make a C program that generates it.
The design goal is to provide setups that are: The design goals are to provide setups that are:
* highly automated: "just works" * highly automated: "just works"
* thoroughly documented: you know what "just works" means * thoroughly documented: you know what "just works" means
@@ -288,7 +288,7 @@ link:https://en.wikipedia.org/wiki/Buildroot[Buildroot] is a set of `make` scrip
* GCC * GCC
* Linux kernel * Linux kernel
* glibc * glibc
* BusyBox * link:https://en.wikipedia.org/wiki/BusyBox[BusyBox]
It therefore produces a pristine, blob-less, debuggable setup, where all moving parts are configured to work perfectly together. It therefore produces a pristine, blob-less, debuggable setup, where all moving parts are configured to work perfectly together.