p/bfc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update READMEs

Browse Source
This commit is contained in:
Přemysl Eric Janouch
2016-12-22 23:40:30 +01:00
parent ea69cc7d9e
commit 99330e88f2
2 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.adoc
View File

@@ -29,8 +29,9 @@ Usage
./bfc-amd64-linux [INPUT-FILE] [OUTPUT-FILE] ./bfc-amd64-linux [INPUT-FILE] [OUTPUT-FILE]
When no input file is specified, stdin is used. Similarly, the default output When no input file is specified, standard input is used. Similarly, the default
filename is a.out. The resulting file can be run on the target platform. output filename is `a.out`. After the compilation, the resulting file can be
run on the target platform.
Contributing and Support Contributing and Support
------------------------ ------------------------

7
interpreters/README.adoc
View File

@@ -9,7 +9,12 @@ sophistication, from the simplest approach to an optimizing JIT compiler:
* `bf-jit-unsafe.c` abolishes all boundary checks when moving across the tape * `bf-jit-unsafe.c` abolishes all boundary checks when moving across the tape
* `bf-jit-unsafe-opt.c` makes use of immediate offsets to modify values * `bf-jit-unsafe-opt.c` makes use of immediate offsets to modify values
I recommend using a tool such as 'meld' to view the differences. I recommend using a tool such as _meld_ to view the differences.
Just run `make` in this directory to have them all built, and append Just run `make` in this directory to have them all built, and append
`CPPFLAGS=-DDEBUG` to get dumps of the IR for the more sophisticated JITs. `CPPFLAGS=-DDEBUG` to get dumps of the IR for the more sophisticated JITs.
The interpreters take the program on standard input and read characters
directly from the terminal device, so to run a simple `cat`-like program,
you can do:
$ echo ',[.,]' | ./bf