fix more broken markdown links
We fix more markdown links in markdown files that refer to files internally to the web site. Added tmp tools to find and print various markdown links: * `tmp/md-links.sh` - print all markdown links * `tmp/md-token-links.sh` - print all markdown links that start with a **%%TOKEN%%** * `tmp/md-local-links.sh` - print all markdown links to a local file * `tmp/md-link-paths.sh` - print local file paths referenced in markdown links Fixed a number of markdown formatting problems with `thanks-for-help.md`. Fixed markdown links to files in `thanks-for-help.md`. Improved heading levels in `thanks-for-help.md`, and made entry sections consistent. Changed all markdown links that end in "))" to end in a better way. Explained in `markdown.md` why we are avoiding markdown links that end in "))". Ran `make www` to perform the above. TODO: Fix stuff we broke by mistake doing the above. TODO: Fix more broken markdown links.
This commit is contained in:
1 parent
60960e1650
commit
4f95e3f3d6
174 files changed
+4008
-2029
No files matched your search
@@ -123,7 +123,7 @@ The build script should give an example command to compile the program.
|
||||
### Features
|
||||
|
||||
[Basic Block](https://en.wikipedia.org/wiki/Basic_block)
|
||||
[Cache](https://en.wikipedia.org/wiki/Cache_(computing)): Rather than
|
||||
[Cache](https://en.wikipedia.org/wiki/Cache_(computing)): Rather than
|
||||
translating each instruction individually the dynamic binary translator
|
||||
generates a translation for an entire basic block of subject code. Having
|
||||
translated a block once, the target code generated will be stored for the
|
||||
@@ -138,7 +138,7 @@ The program runs [dynamically
|
||||
linked](https://en.wikipedia.org/wiki/Dynamic_linker) [ELF
|
||||
binaries](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format), and
|
||||
when the subject program attempts to make a call to a standard
|
||||
[library](https://en.wikipedia.org/wiki/Library_(computing)), the translator
|
||||
[library](https://en.wikipedia.org/wiki/Library_(computing)), the translator
|
||||
attempts to make an appropriate call to the native system libraries on the
|
||||
target machine. This involves mangling between different calling conventions,
|
||||
etc.
|
||||
@@ -209,9 +209,9 @@ on to the next line of code.
|
||||
Due to space limitations only a handful of instructions are supported; these
|
||||
instructions which are supported are supported in somewhat non-conventional
|
||||
ways: chunks of the architecture (e.g. flags) are just ignored, the ELF
|
||||
[loader](https://en.wikipedia.org/wiki/Loader_(computing)) does not really load
|
||||
[loader](https://en.wikipedia.org/wiki/Loader_(computing)) does not really load
|
||||
the [ELF binary](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format),
|
||||
the target [library linking](https://en.wikipedia.org/wiki/Linker_(computing))
|
||||
the target [library linking](https://en.wikipedia.org/wiki/Linker_(computing))
|
||||
can only pass up to 3 parameters to the target library function, etc.
|
||||
|
||||
In short, please consider this a full disclaimer for any bug that may
|
||||
|
||||
@@ -53,8 +53,8 @@ You can use it by typing:
|
||||
|
||||
or by giving the C source to its standard input.
|
||||
|
||||
`args` are given to the `main()` function of `bellard.c` (`argv[0]` is
|
||||
[bellard.c](%%REPO_URL%%/2001/bellard/bellard.c)).
|
||||
`args` are given to the `main()` function of `bellard.c`, `argv[0]` is
|
||||
[bellard.c](%%REPO_URL%%/2001/bellard/bellard.c).
|
||||
|
||||
|
||||
### Examples:
|
||||
|
||||
@@ -420,8 +420,8 @@ program.</p>
|
||||
<p>You can use it by typing:</p>
|
||||
<pre><code> ./bellard bellard.c [args]...</code></pre>
|
||||
<p>or by giving the C source to its standard input.</p>
|
||||
<p><code>args</code> are given to the <code>main()</code> function of <code>bellard.c</code> (<code>argv[0]</code> is
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/bellard/bellard.c">bellard.c</a>).</p>
|
||||
<p><code>args</code> are given to the <code>main()</code> function of <code>bellard.c</code>, <code>argv[0]</code> is
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/bellard/bellard.c">bellard.c</a>.</p>
|
||||
<h3 id="examples">Examples:</h3>
|
||||
<ul>
|
||||
<li>Sample compilation and execution:</li>
|
||||
|
||||
@@ -162,7 +162,7 @@ program would probably be rated somewhere around 1700-1900. It is better
|
||||
than most players, but will get destroyed by experienced human opponents.
|
||||
|
||||
This program searches to a fixed depth of 3
|
||||
[ply](https://en.wikipedia.org/wiki/Ply_(game_theory)). Because it does not
|
||||
[ply](https://en.wikipedia.org/wiki/Ply_(game_theory)). Because it does not
|
||||
search very deep, it performs very poorly in quiet strategic positions.
|
||||
In such positions, it will often just shuffle pieces around aimlessly
|
||||
until a tactical exchange presents itself.
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
```
|
||||
|
||||
If you use vi(m) you can see a pattern in [herrmann2.cup](%%REPO_URL%%/2001/herrmann2/herrmann2.cup) and
|
||||
[herrmann2.ioccc][(%%REPO_URL%%/2001/herrmann2/herrmann2.ioccc]) by say:
|
||||
[herrmann2.ioccc][(%%REPO_URL%%/2001/herrmann2/herrmann2.ioccc] by say:
|
||||
|
||||
|
||||
```
|
||||
|
||||
@@ -404,7 +404,7 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
|
||||
<h2 id="try">Try:</h2>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<p>If you use vi(m) you can see a pattern in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2/herrmann2.cup">herrmann2.cup</a> and
|
||||
[herrmann2.ioccc][(https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2/herrmann2.ioccc]) by say:</p>
|
||||
[herrmann2.ioccc][(https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2/herrmann2.ioccc] by say:</p>
|
||||
<pre><code> /[pon]\</code></pre>
|
||||
<p>and</p>
|
||||
<pre><code> /l</code></pre>
|
||||
|
||||
Reference in new issue
Block a user