mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

force use of pandoc version >= 3.1.12.2

Browse Source 
The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2020/yang/index.html
+64 -97
View File
@@ -130,8 +130,8 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Don_Yang">Don Yang</a><br>
Location: <a href="../../location.html#US">US</a> - <em>United States of
America</em> (<em>United States</em>) <br><br></li>
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -145,71 +145,62 @@ America</em> (<em>United States</em>) <br><br></li>
<div class="sourceCode" id="cb2"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./prog</span> <span class="pp">[</span><span class="ss">PIN</span><span class="pp">]</span> <span class="op">&lt;</span> input.txt <span class="op">&gt;</span> output.c</span></code></pre></div>
<h2 id="try">Try:</h2>
<div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.sh</span></span></code></pre></div>
<p>The author provided the file <a href="cppp.cc">cppp.cc</a> which can
preprocess the generated output to make them more acceptable to typical
compilers. To build:</p>
<p>The author provided the file <a href="cppp.cc">cppp.cc</a> which can preprocess the
generated output to make them more acceptable to typical compilers. To build:</p>
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="fu">make</span> cppp</span></code></pre></div>
<p>See the author’s remarks for more details.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>You might think of this entry as code obfuscater with a code. If you
use the wrong code, you’re gonna have a bad time. What is compiling this
entry about? <a
href="https://southpark.fandom.com/wiki/Asspen/Script">Having a good ..
time</a>!</p>
<p>This winning entry also comes with a <a
href="spoiler.html">JavaScript timelapse spoiler</a> that shows how this
entry was written.</p>
<p>You might think of this entry as code obfuscater with a code.
If you use the wrong code, you’re gonna have a bad time.
What is compiling this entry about?
<a href="https://southpark.fandom.com/wiki/Asspen/Script">Having a good .. time</a>!</p>
<p>This winning entry also comes with a <a href="spoiler.html">JavaScript timelapse
spoiler</a> that shows how this entry was written.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<h3 id="synopsis">Synopsis</h3>
<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="bu">echo</span> <span class="st">&quot;Hello world&quot;</span> <span class="kw">|</span> <span class="ex">./prog</span> 12345 <span class="op">&gt;</span> encoded.c</span>
<span id="cb5-2"><a href="#cb5-2" aria-hidden="true" tabindex="-1"></a></span>
<span id="cb5-3"><a href="#cb5-3" aria-hidden="true" tabindex="-1"></a><span class="fu">gcc</span> <span class="at">-DPIN</span><span class="op">=</span>12345 encoded.c <span class="at">-o</span> ./decoded <span class="kw">&amp;&amp;</span> <span class="ex">./decoded</span></span></code></pre></div>
<h3 id="details">Details</h3>
<p>Mile is a C code generator. Run without arguments for the help
message below:</p>
<p>Mile is a C code generator. Run without arguments for the help message below:</p>
<pre><code>usage: [PIN] &lt; input.txt &gt; output.c
where [PIN] is an integer in the range of 1..65535</code></pre>
<p>When run with an encoding PIN (first command line argument), Mile
will read bytes from <code>stdin</code> and generate C code on
<code>stdout</code>. Example:</p>
<p>When run with an encoding PIN (first command line argument), Mile will
read bytes from <code>stdin</code> and generate C code on <code>stdout</code>. Example:</p>
<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="bu">echo</span> <span class="st">&quot;Hello, world!&quot;</span> <span class="kw">|</span> <span class="ex">./prog</span> 56789 <span class="op">&gt;</span> encoded.c</span></code></pre></div>
<p>This generated code will reproduce the same input bytes on
<code>stdout</code> when executed, if it was compiled with the same
encoding PIN.</p>
<p>This generated code will reproduce the same input bytes on <code>stdout</code> when
executed, if it was compiled with the same encoding PIN.</p>
<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="fu">gcc</span> <span class="at">-DPIN</span><span class="op">=</span>56789 encoded.c <span class="at">-o</span> decoded</span></code></pre></div>
<p>The generated code reconstructs all data at compile time by seeding a
random number generator with the given PIN to reproduce the input bytes,
and simply does one <code>fwrite(3)</code> call at run time to print
those bytes. Not specifying a PIN is a compile time error. Specify the
wrong PIN and output code will still compile, but will likely produce
garbage instead of the input bytes. If the original input was empty then
any PIN works, but you might get a compile time warning complaining
about empty arrays.</p>
<p>Because all data is reconstructed at compile time, expect the compile
time to be excruciatingly long if you try to encode too much data. Code
generated by encoding a haiku will probably compile in seconds, a
limerick may require tens of seconds, a sonnet will take minutes. Give
Mile an epic poem and you can probably write a faster preprocessor
before GCC is done (Clang probably already failed long before then).</p>
<p>I see that there is a lack of preprocessor abuse in recent years,
probably because programming in preprocessor is too tedious. Mile is
meant to help with that by producing C code filled with at least 98%
preprocessor lines for any input. Now you too can enjoy long compile
times with minimal effort.</p>
and simply does one <code>fwrite(3)</code> call at run time to print those bytes. Not
specifying a PIN is a compile time error. Specify the wrong PIN and
output code will still compile, but will likely produce garbage instead of
the input bytes. If the original input was empty then any PIN works, but
you might get a compile time warning complaining about empty arrays.</p>
<p>Because all data is reconstructed at compile time, expect the compile time
to be excruciatingly long if you try to encode too much data. Code
generated by encoding a haiku will probably compile in seconds, a limerick
may require tens of seconds, a sonnet will take minutes. Give Mile an
epic poem and you can probably write a faster preprocessor before GCC is
done (Clang probably already failed long before then).</p>
<p>I see that there is a lack of preprocessor abuse in recent years, probably
because programming in preprocessor is too tedious. Mile is meant to help
with that by producing C code filled with at least 98% preprocessor lines
for any input. Now you too can enjoy long compile times with minimal
effort.</p>
<h3 id="features">Features</h3>
<ul>
<li><p>Output is randomized using system clock, so if you wait a second
between runs, you should get a different generated code even for the
same encoding PIN.</p></li>
<li><p>Customized bytecode encoding of preprocessor boilerplates, mostly
for compression but should also make reverse engineering more
fun.</p></li>
<li><p>CRC32 of the source code is embedded in the source code
itself.</p></li>
<li><p>Code layout shaped to resemble “Mile” from “Didn’t I Say to Make
My Abilities Average in the Next Life?!”. Mile is known to be able to
talk to nanomachines directly, which is exactly what programming in
<li><p>Output is randomized using system clock, so if you wait a second between
runs, you should get a different generated code even for the same
encoding PIN.</p></li>
<li><p>Customized bytecode encoding of preprocessor boilerplates, mostly for
compression but should also make reverse engineering more fun.</p></li>
<li><p>CRC32 of the source code is embedded in the source code itself.</p></li>
<li><p>Code layout shaped to resemble “Mile” from “Didn’t I Say to Make My
Abilities Average in the Next Life?!”. Mile is known to be able to talk
to nanomachines directly, which is exactly what programming in
preprocessor feels like.</p></li>
</ul>
<h3 id="compatibility">Compatibility</h3>
@@ -226,73 +217,49 @@ without warnings on all of these):</p>
<li>tcc 0.9.27 on Linux</li>
<li>tcc 0.9.25 on JSLinux</li>
</ul>
<p>Output of Mile is a bit more taxing, and only works with a subset of
the above:</p>
<p>Output of Mile is a bit more taxing, and only works with a subset of the
above:</p>
<ul>
<li>gcc: works just fine when using 8.3.0 and below, but may trigger
warning for large files. gcc 9.2.0 and above may crash with large
files.</li>
<li>clang: works fine for small files, fails on large files due to <a
href="https://bugs.llvm.org/show_bug.cgi?id=44480">preprocessor
bug</a>.</li>
<li>gcc: works just fine when using 8.3.0 and below, but may trigger warning
for large files. gcc 9.2.0 and above may crash with large files.</li>
<li>clang: works fine for small files, fails on large files due to
<a href="https://bugs.llvm.org/show_bug.cgi?id=44480">preprocessor bug</a>.</li>
<li>tcc: works just fine on Linux. Fails silently on JSLinux.</li>
</ul>
<p>For people eager to encode large files, an extra utility has been
packaged with this entry to preprocess the generated output to make them
more acceptable to typical compilers. View the <a
href="cppp.cc">cppp.cc</a> source and then compile it with a c++
compiler of your choice.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
Reserved. You are free to share and adapt this file under the terms of
this license:</p>
<p>For people eager to encode large files, an extra utility has been packaged
with this entry to preprocess the generated output to make them more
acceptable to typical compilers. View the <a href="cppp.cc">cppp.cc</a> source and
then compile it with a c++ compiler of your choice.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:</p>
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
<p>For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/</p>
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</p>
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
<h1 id="inventory-for-2020yang"><a name="inventory"></a>Inventory for
2020/yang</h1>
<h1 id="inventory-for-2020yang"><a name="inventory"></a>Inventory for 2020/yang</h1>
<p><a href="#top">Jump to top</a></p>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/prog.c">prog.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/prog.orig.c">prog.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/try.sh">try.sh</a>
- how to run</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/cppp.cc">cppp.cc</a>
- encode large file C Pre-PreProcessor source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/prog.c">prog.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/prog.orig.c">prog.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/try.sh">try.sh</a> - how to run</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/cppp.cc">cppp.cc</a> - encode large file C Pre-PreProcessor source</li>
<li><a href="spoiler.html">spoiler.html</a> - SPOILER WARNING</li>
<li><a href="2020_yang.tar.bz2">2020_yang.tar.bz2</a> - download entry
source</li>
<li><a href="2020_yang.tar.bz2">2020_yang.tar.bz2</a> - download entry source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="index.html">index.html</a> - entry home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/.gitignore">.gitignore</a>
- list of files that should not be committed under git</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
<li><a href=".path">.path</a> - directory path from top directory</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/yang/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->