diff options
author | Andreas Baumann <mail@andreasbaumann.cc> | 2021-10-13 20:32:29 +0200 |
---|---|---|
committer | Andreas Baumann <mail@andreasbaumann.cc> | 2021-10-13 20:32:29 +0200 |
commit | 62924274b391dbfd16f4349bd46a2136f2a78b0e (patch) | |
tree | 0a5aefa2d23bf402fff822f5bc2f93743cfaf1b4 /miniany/README.html | |
parent | f895cabf52336db0f2a259bbe6fae6e6fc81c98a (diff) | |
download | compilertests-62924274b391dbfd16f4349bd46a2136f2a78b0e.tar.gz compilertests-62924274b391dbfd16f4349bd46a2136f2a78b0e.tar.bz2 |
cc: some support for putchar and char store/load
Diffstat (limited to 'miniany/README.html')
-rw-r--r-- | miniany/README.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/miniany/README.html b/miniany/README.html index 7be5708..ca5cdf7 100644 --- a/miniany/README.html +++ b/miniany/README.html @@ -12,7 +12,7 @@ <p>Similarly we simplify the C language to not use certain features which can cause trouble when bootstrapping:</p> <ul> <li><i>variable </i><i>arguments</i>: though simple in principle (just some pointers into the stack if you use a stack for function parameters), it is not typesafe. And the only example in practice it's really heavily used for is in printf-like functions.</li> -<li><i>preprocessor</i>: it needs a filesystem, we take this outside of the compiler by feeding it an (eventually) concatenated list of *.c files. Note: in the hosted environemt we (and glibc) can use as many preprocessor features as they want, they just don't have to get visible in our code.</li> +<li><i>preprocessor</i>: it needs a filesystem, we take this outside of the compiler by feeding it an (eventually) concatenated list of *.c files. Note: in the hosted environment we (and glibc) can use as many preprocessor features as they want, they just don't have to get visible in our code.</li> <li><i>two </i><i>types</i>: int and char, so we can interpret memory as words or as bytes.</li> </ul> <h2>Local version of C4</h2> @@ -34,7 +34,7 @@ <li>de-POSIX-ified, no <i>open/read/close</i>, use <i>getchar </i>from stdin only (don't assume the existence of a file system), this also means we had to create sort of an old style tape-file with FS markers to separate the files piped to c4.</li> </ul> <p>The reason for all those adaptions is to minimize the dependency on the host system and to be able to use <i>libc-freestanding.c</i>.</p> -<h3><i>Note: </i>only too late I discovered that there was a C5 version of the same compiler, which would maybe have served better as a basis.</h3> +<p>Note: Only too late I discovered that there was a C5 version of the same compiler, which would maybe have served better as a basis.</p> <h2>Examples</h2> <h3>Running on the host system using the hosts C compiler</h3> <p>Compiled in either hosted (host libc) or freestanding (our own libc, currently IA-32 Linux kernel only syscalls):</p> |