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

Merge pull request #2696 from xexyl/html15

Browse Source 
Format fix html files in 2015, update bugs file
This commit is contained in:
Landon Curt Noll authored and GitHub committed 2024-10-15 09:58:00 -07:00
2 parents 1c59b16b70 ea00ce2409
commit 18268ae452
12 files changed
+104 -72
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2015/burton/README.md
+5 -1
View File
@@ -4,6 +4,10 @@
make
```
There is an alternate version which the author discusses in their
[prog.c vs prog.alt.c](#prog.c-vs-prog.alt.c) section. See [Alternate
code](#alternate-code) below.
## To use:
@@ -89,7 +93,7 @@ written on an `iDevice`), but sanity prevailed.
Printed in 8 pt Courier, it makes aesthetically pleasing 8.5 x 11 wall art.
[1]: ../../2011/hou/hint.html "Hou Qiming"
[1]: ../../2011/hou/index.html "Hou Qiming"
### prog.c vs prog.alt.c
2015/burton/index.html
+4 -1
View File
@@ -410,6 +410,9 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 2015/burton/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make</code></pre>
<p>There is an alternate version which the author discusses in their
<a href="#prog.c-vs-prog.alt.c">prog.c vs prog.alt.c</a> section. See <a href="#alternate-code">Alternate
code</a> below.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./prog &quot;expression&quot;</code></pre>
<p>or:</p>
@@ -442,7 +445,7 @@ process.</p>
See the included man page. ;-)</p>
<h3 id="notes">Notes</h3>
<p>This program is named <code>calc</code>. Onomatopoeia of sorts, in the visual realm. The
formatting was easier: Form Follows Function (although <a href="../../2011/hou/hint.html" title="Hou Qiming">Hou</a> did this
formatting was easier: Form Follows Function (although <a href="../../2011/hou/index.html" title="Hou Qiming">Hou</a> did this
better). It was tempting to call it iCalc, with <code>i</code> for integer (and it was
written on an <code>iDevice</code>), but sanity prevailed.</p>
<p>Printed in 8 pt Courier, it makes aesthetically pleasing 8.5 x 11 wall art.</p>
2015/dogon/README.md
+4 -7
View File
@@ -70,11 +70,8 @@ Press the ESC key.
The author suggested that one change `q` to `0x82000820000000` instead of
`0x820008202625a0` to see a bug that they avoided, writing:
```
To see this bug in action change the assignment above
to q=0x82000820000000`, and look towards the negative
direction of the main tunnel.
```
> To see this bug in action change the assignment above to `q=0x82000820000000`,
and look towards the negative direction of the main tunnel.
This alt version does this for you.
@@ -107,7 +104,7 @@ Can you find your way around either and understand where you are?
How many function keys does your keyboard have? Can you generate very high
number function keys such as F30 or F31? :-)
*Textures? We don't need no stinking textures.*
_Textures? We don't need no stinking textures._
## Author's remarks:
@@ -184,7 +181,7 @@ the following:
### Precision issues:
The entry, on purpose, (see the section about SIMD below) does not use enough
The entry, on purpose (see the section about SIMD below), does not use enough
bits of precision, so sometimes the ray will miss the intersection of two voxel
faces and push on through. That's why you may notice some noise along close up
voxel edges. Fixing this issue would have taken the entry over the size limit
2015/dogon/index.html
+5 -4
View File
@@ -442,9 +442,10 @@ again.</p>
<h2 id="alternate-code">Alternate code:</h2>
<p>The author suggested that one change <code>q</code> to <code>0x82000820000000</code> instead of
<code>0x820008202625a0</code> to see a bug that they avoided, writing:</p>
<pre><code> To see this bug in action change the assignment above
to q=0x82000820000000`, and look towards the negative
direction of the main tunnel.</code></pre>
<blockquote>
<p>To see this bug in action change the assignment above to <code>q=0x82000820000000</code>,
and look towards the negative direction of the main tunnel.</p>
</blockquote>
<p>This alt version does this for you.</p>
<h3 id="alternate-build">Alternate build:</h3>
<pre><code> make alt</code></pre>
@@ -519,7 +520,7 @@ the following:</li>
</ul>
<pre><code> *(a&amp;1?&amp;C:&amp;B)-=(.05 -a/2%2*.1)*!(a-1&amp;4092^3920)</code></pre>
<h3 id="precision-issues">Precision issues:</h3>
<p>The entry, on purpose, (see the section about SIMD below) does not use enough
<p>The entry, on purpose (see the section about SIMD below), does not use enough
bits of precision, so sometimes the ray will miss the intersection of two voxel
faces and push on through. That’s why you may notice some noise along close up
voxel edges. Fixing this issue would have taken the entry over the size limit
2015/duble/README.md
+9
View File
@@ -8,6 +8,15 @@ There is an alternate version of this entry, discussed in the author's remarks.
See [Alternate code](#alternate-code) below.
### Bugs and (Mis)features:
The current status of this entry is:
> **STATUS: INABIAF - please DO NOT fix**
For more detailed information see [2015/duble in bugs.html](../../bugs.html#2015_duble).
## To use:
``` <!---sh-->
2015/duble/index.html
+6
View File
@@ -412,6 +412,12 @@ Location: <a href="../../location.html#FR">FR</a> - <em>French Republic</em> (<e
<pre><code> make</code></pre>
<p>There is an alternate version of this entry, discussed in the author’s remarks.
See <a href="#alternate-code">Alternate code</a> below.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<blockquote>
<p><strong>STATUS: INABIAF - please DO NOT fix</strong></p>
</blockquote>
<p>For more detailed information see <a href="../../bugs.html#2015_duble">2015/duble in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
<pre><code> echo Some text | ./prog</code></pre>
<h2 id="try">Try:</h2>
2015/endoh3/README.md
+1 -1
View File
@@ -14,7 +14,7 @@
## Try:
To see the original [mullender](%%REPO_URL%%/2015/endoh3/mullender.c) in action:
To see the original [mullender](../../1984/mullender/index.html) in action:
``` <!---sh-->
./try.sh
2015/endoh3/index.html
+1 -1
View File
@@ -413,7 +413,7 @@ Location: <a href="../../location.html#JP">JP</a> - <em>Japan</em></li>
<h2 id="to-use">To use:</h2>
<pre><code> ./prog</code></pre>
<h2 id="try">Try:</h2>
<p>To see the original <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/endoh3/mullender.c">mullender</a> in action:</p>
<p>To see the original <a href="../../1984/mullender/index.html">mullender</a> in action:</p>
<pre><code> ./try.sh</code></pre>
<p>Observe what happens when you hit enter or another character! You might even try
typing out, one character at a time, <code>1984/mullender</code>, and then see what it looks
2015/mills1/README.md
+1 -1
View File
@@ -76,7 +76,7 @@ From the Makefile:
# NOTE: The string MUST be enclosed inside double quotes.
```
WARNING: if you have good eye-hand coordination and too much time on your hands
**WARNING**: if you have good eye-hand coordination and too much time on your hands
you might fall asleep while playing as you probably will never die in this mode.
We only stopped when a reminder came through and we tried to mark it complete at
the same time as playing and we almost managed to survive that. At that point we
2015/mills1/index.html
+1 -1
View File
@@ -456,7 +456,7 @@ bit easier for you:</p>
DG=&#39;&quot;Tap to Flap!&quot;&#39; # Instruction text.
# Change to your native tongue.
# NOTE: The string MUST be enclosed inside double quotes.</code></pre>
<p>WARNING: if you have good eye-hand coordination and too much time on your hands
<p><strong>WARNING</strong>: if you have good eye-hand coordination and too much time on your hands
you might fall asleep while playing as you probably will never die in this mode.
We only stopped when a reminder came through and we tried to mark it complete at
the same time as playing and we almost managed to survive that. At that point we
bugs.html
+40 -32
View File
@@ -2961,14 +2961,22 @@ rely on the entry as the below shows. One should be able to do:</p>
<h1 id="section-31">2015</h1>
</div>
<hr style="width:10%;text-align:left;margin-left:0">
<div id="2015_duble">
<h2 id="duble">2015/duble</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-77">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2015dubleprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/duble/prog.c">2015/duble/prog.c</a></h3>
<h3 id="information-2015dubleindex.html">Information: <a href="2015/duble/index.html">2015/duble/index.html</a></h3>
<p>This program is known to, in some cases, segfault, and as the judges and the
author noted this, it should not be fixed.</p>
<div id="2015_hou">
<h2 id="hou-1">2015/hou</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-77">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-78">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2015houprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/hou/prog.c">2015/hou/prog.c</a></h3>
<h3 id="information-2015houindex.html">Information: <a href="2015/hou/index.html">2015/hou/index.html</a></h3>
<p>The author stated:</p>
<p>–</p>
<blockquote>
<p>Hard requirements:</p>
<ul>
<li><p>The platform must implement the <code>double</code> type as IEEE754-compliant 64-bit
@@ -2985,7 +2993,7 @@ that, though.</p></li>
takes care to warn about this issue after printing an incorrect big-endian
result. Error messages become garbled, though.</p></li>
</ul>
<p>–</p>
</blockquote>
<div id="2015_howe">
<h2 id="howe">2015/howe</h2>
</div>
@@ -3008,7 +3016,7 @@ because it is the same thing as the other, just updated to use <code>prog.alt</c
<div id="2015_mills2">
<h2 id="mills2">2015/mills2</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-78">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-79">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2015mills2prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/mills2/prog.c">2015/mills2/prog.c</a></h3>
<h3 id="information-2015mills2index.html">Information: <a href="2015/mills2/index.html">2015/mills2/index.html</a></h3>
<p>The program doesn’t look at the header of files so if it’s passed something hat
@@ -3017,19 +3025,19 @@ is not compressed data it’s likely to crash.</p>
<div id="2015_schweikhardt">
<h2 id="schweikhardt">2015/schweikhardt</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-79">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-80">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2015schweikhardtprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2015/schweikhardt/prog.c">2015/schweikhardt/prog.c</a></h3>
<h3 id="information-2015schweikhardtindex.html">Information: <a href="2015/schweikhardt/index.html">2015/schweikhardt/index.html</a></h3>
<p>The program assumes that <code>EOF</code> is <code>-1</code>. This can be fixed but at this time it is
uncertain if it should be.</p>
<p>The author also stated:</p>
<p>–</p>
<p>While the program works best when bytes/characters are octets and the
number of bits in a type is <code>sizeof(typ) &lt;&lt; 3</code>, it will work correctly
on 24-bit or 36-bit systems with 9 bits/byte, or systems where
<code>sizeof(typ)</code> is 1 even for <code>int</code> and so on. On such systems, it will only
use <code>8 * sizeof(typ)</code> bits per place. It does not work when <code>CHAR_BIT &lt;= 7</code>.</p>
<p>–</p>
<blockquote>
<p>While the program works best when bytes/characters are octets and the number
of bits in a type is <code>sizeof(typ) &lt;&lt; 3</code>, it will work correctly on 24-bit or
36-bit systems with 9 bits/byte, or systems where <code>sizeof(typ)</code> is 1 even for
<code>int</code> and so on. On such systems, it will only use <code>8 * sizeof(typ)</code> bits per
place. It does not work when <code>CHAR_BIT &lt;= 7</code>.</p>
</blockquote>
<hr style="width:10%;text-align:left;margin-left:0">
<div id="2016">
<h1 id="section-32">2016</h1>
@@ -3050,7 +3058,7 @@ use <code>8 * sizeof(typ)</code> bits per place. It does not work when <code>CHA
<div id="2018_algmyr">
<h2 id="algmyr">2018/algmyr</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-80">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-81">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2018algmyrprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/algmyr/prog.c">2018/algmyr/prog.c</a></h3>
<h3 id="information-2018algmyrindex.html">Information: <a href="2018/algmyr/index.html">2018/algmyr/index.html</a></h3>
<p>The author wrote:</p>
@@ -3069,7 +3077,7 @@ loop printing whitespace.</li>
<div id="2018_hou">
<h2 id="hou-2">2018/hou</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-81">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-82">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2018houprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/hou/prog.c">2018/hou/prog.c</a></h3>
<h3 id="information-2018houindex.html">Information: <a href="2018/hou/index.html">2018/hou/index.html</a></h3>
<p>When you run it on a JSON file you will see something like:</p>
@@ -3094,7 +3102,7 @@ likely see:</p>
<p>where <code>[]</code> is the cursor. When this happens if you hit enter (this is necessary
or else it’ll happen again) and then exit again (ctrl-e) and run <code>prog</code> again
it’ll be okay.</p>
<h3 id="status-inabiaf---please-do-not-fix-82">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-83">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<p>The author stated that if you make a typo it can happen that the boot loader can
crash and halt. If this is the case type ctrl-e to quit the emulator and try
again.</p>
@@ -3109,7 +3117,7 @@ in the case of compiled code it won’t be executable).</p>
<div id="2018_vokes">
<h2 id="vokes">2018/vokes</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-83">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-84">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2018vokesprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2018/vokes/prog.c">2018/vokes/prog.c</a></h3>
<h3 id="information-2018vokesindex.html">Information: <a href="2018/vokes/index.html">2018/vokes/index.html</a></h3>
<p>The author wrote the following:</p>
@@ -3159,7 +3167,7 @@ this program has nothing to do with a hand.</p></li>
<div id="2019_adamovsky">
<h2 id="adamovsky">2019/adamovsky</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-84">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-85">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019adamovskyprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/adamovsky/prog.c">2019/adamovsky/prog.c</a></h3>
<h3 id="information-2019adamovskyindex.html">Information: <a href="2019/adamovsky/index.html">2019/adamovsky/index.html</a></h3>
<p>Certain input can crash this program. The file
@@ -3167,7 +3175,7 @@ this program has nothing to do with a hand.</p></li>
<div id="2019_burton">
<h2 id="burton">2019/burton</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-85">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-86">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019burtonprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/burton/prog.c">2019/burton/prog.c</a></h3>
<h3 id="information-2019burtonindex.html">Information: <a href="2019/burton/index.html">2019/burton/index.html</a></h3>
<p>The author pointed out that some implementations of <code>wc(1)</code> show different
@@ -3175,7 +3183,7 @@ values but his implementation matches that of macOS and FreeBSD.</p>
<div id="2019_ciura">
<h2 id="ciura">2019/ciura</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-86">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-87">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019ciuraprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/ciura/prog.c">2019/ciura/prog.c</a></h3>
<h3 id="information-2019ciuraindex.html">Information: <a href="2019/ciura/index.html">2019/ciura/index.html</a></h3>
<p><a href="authors.html#Cody_Boone_Ferguson">Cody Boone Ferguson</a> fixed the scripts so
@@ -3207,9 +3215,9 @@ in the de.sh/de.alt.sh scripts:</p>
FAQ on “<a href="faq.html#gets">gets and fgets</a>”
for more information on the change to <code>fgets(3)</code>.</p>
<div id="2019_duble">
<h2 id="duble">2019/duble</h2>
<h2 id="duble-1">2019/duble</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-87">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-88">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019dubleprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/duble/prog.c">2019/duble/prog.c</a></h3>
<h3 id="information-2019dubleindex.html">Information: <a href="2019/duble/index.html">2019/duble/index.html</a></h3>
<p>There are two things to be aware of with this entry.</p>
@@ -3238,7 +3246,7 @@ in the directory:</p>
<div id="2019_endoh">
<h2 id="endoh">2019/endoh</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-88">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-89">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019endohprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/endoh/prog.c">2019/endoh/prog.c</a></h3>
<h3 id="information-2019endohindex.html">Information: <a href="2019/endoh/index.html">2019/endoh/index.html</a></h3>
<p>As a backtrace quine this entry is <strong>SUPPOSED to segfault</strong> so this should not be
@@ -3246,7 +3254,7 @@ touched either.</p>
<div id="2019_karns">
<h2 id="karns">2019/karns</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-89">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-90">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019karnsprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/karns/prog.c">2019/karns/prog.c</a></h3>
<h3 id="information-2019karnsindex.html">Information: <a href="2019/karns/index.html">2019/karns/index.html</a></h3>
<p>The author stated the following:</p>
@@ -3276,7 +3284,7 @@ touched either.</p>
<div id="2019_lynn">
<h2 id="lynn">2019/lynn</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-90">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-91">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019lynnprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/lynn/prog.c">2019/lynn/prog.c</a></h3>
<h3 id="information-2019lynnindex.html">Information: <a href="2019/lynn/index.html">2019/lynn/index.html</a></h3>
<p>The author wrote that there are a number of differences from what one might
@@ -3286,7 +3294,7 @@ remarks in the sections <a href="2019/lynn/index.html#syntax">Syntax</a> and
<div id="2019_mills">
<h2 id="mills-2">2019/mills</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-91">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-92">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019millsprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/mills/prog.c">2019/mills/prog.c</a></h3>
<h3 id="information-2019millsindex.html">Information: <a href="2019/mills/index.html">2019/mills/index.html</a></h3>
<p>The author wrote that if you decide to change networks or use a different input
@@ -3306,7 +3314,7 @@ a crash.</p>
<div id="2019_poikola">
<h2 id="poikola">2019/poikola</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-92">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-93">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019poikolaprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/poikola/prog.c">2019/poikola/prog.c</a></h3>
<h3 id="information-2019poikolaindex.html">Information: <a href="2019/poikola/index.html">2019/poikola/index.html</a></h3>
<p>This program will not validate input so it might fail or get stuck if invoked
@@ -3315,7 +3323,7 @@ erroneously.</p>
<div id="2019_yang">
<h2 id="yang">2019/yang</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-93">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-94">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2019yangprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2019/yang/prog.c">2019/yang/prog.c</a></h3>
<h3 id="information-2019yangindex.html">Information: <a href="2019/yang/index.html">2019/yang/index.html</a></h3>
<p>The author noted that if the program runs out of memory it is likely to crash.</p>
@@ -3330,7 +3338,7 @@ ignored except line feeds (preserved) and tabs (expanded to 8 spaces).’</p>
<div id="2020_burton">
<h2 id="burton-1">2020/burton</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-94">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-95">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2020burtonprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/burton/prog.c">2020/burton/prog.c</a></h3>
<h3 id="information-2020burtonindex.html">Information: <a href="2020/burton/index.html">2020/burton/index.html</a></h3>
<p>This entry is known to crash if no arg is specified. Although easy to fix it is
@@ -3341,7 +3349,7 @@ either. But can you figure out why this happens?</p>
<div id="2020_carlini">
<h2 id="carlini">2020/carlini</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-95">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-96">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2020carliniprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/carlini/prog.c">2020/carlini/prog.c</a></h3>
<h3 id="information-2020carliniindex.html">Information: <a href="2020/carlini/index.html">2020/carlini/index.html</a></h3>
<p>The author stated that bad things happen if the entered move is outside of the
@@ -3355,7 +3363,7 @@ move.</p>
<div id="2020_ferguson1">
<h2 id="ferguson1">2020/ferguson1</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-96">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-97">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2020ferguson1prog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/ferguson1/prog.c">2020/ferguson1/prog.c</a></h3>
<h3 id="information-2020ferguson1index.html">Information: <a href="2020/ferguson1/index.html">2020/ferguson1/index.html</a></h3>
<p>There are some things that might appear to be bugs but are actually features or
@@ -3365,7 +3373,7 @@ things that are misinterpreted as bugs. See the
<div id="2020_giles">
<h2 id="giles">2020/giles</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-97">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-98">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2020gilesprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/giles/prog.c">2020/giles/prog.c</a></h3>
<h3 id="information-2020gilesindex.html">Information: <a href="2020/giles/index.html">2020/giles/index.html</a></h3>
<p>The author noted that the program only supports WAV files that have
@@ -3374,7 +3382,7 @@ audio channels.</p>
<div id="2020_otterness">
<h2 id="otterness">2020/otterness</h2>
</div>
<h3 id="status-inabiaf---please-do-not-fix-98">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="status-inabiaf---please-do-not-fix-99">STATUS: INABIAF - please <strong>DO NOT</strong> fix</h3>
<h3 id="source-code-2020otternessprog.c">Source code: <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2020/otterness/prog.c">2020/otterness/prog.c</a></h3>
<h3 id="information-2020otternessindex.html">Information: <a href="2020/otterness/index.html">2020/otterness/index.html</a></h3>
<p>The author listed the following limitations:</p>
bugs.md
+27 -23
View File
@@ -3704,6 +3704,17 @@ they will properly get:
<hr style="width:10%;text-align:left;margin-left:0">
<div id="2015_duble">
## 2015/duble
</div>
### STATUS: INABIAF - please **DO NOT** fix
### Source code: [2015/duble/prog.c](%%REPO_URL%%/2015/duble/prog.c)
### Information: [2015/duble/index.html](2015/duble/index.html)
This program is known to, in some cases, segfault, and as the judges and the
author noted this, it should not be fixed.
<div id="2015_hou">
## 2015/hou
@@ -3715,27 +3726,24 @@ they will properly get:
The author stated:
--
Hard requirements:
* The platform must implement the `double` type as IEEE754-compliant 64-bit
> Hard requirements:
>
> * The platform must implement the `double` type as IEEE754-compliant 64-bit
floating point numbers. The 80-bit intermediate format used by x87 is
considered as an violation of this. The code should print an error message on
such platforms.
* The program must start with the CPU / FPU in round-to-nearest mode.
Soft requirements:
* The compiler must respect `volatile`. The code is formatted to warn about
>
> * The program must start with the CPU / FPU in round-to-nearest mode.
>
> Soft requirements:
>
> * The compiler must respect `volatile`. The code is formatted to warn about
that, though.
* The printed result is only correct on little-endian machines. The program
>
> * The printed result is only correct on little-endian machines. The program
takes care to warn about this issue after printing an incorrect big-endian
result. Error messages become garbled, though.
--
<div id="2015_howe">
## 2015/howe
@@ -3792,15 +3800,11 @@ uncertain if it should be.
The author also stated:
--
While the program works best when bytes/characters are octets and the
number of bits in a type is `sizeof(typ) << 3`, it will work correctly
on 24-bit or 36-bit systems with 9 bits/byte, or systems where
`sizeof(typ)` is 1 even for `int` and so on. On such systems, it will only
use `8 * sizeof(typ)` bits per place. It does not work when `CHAR_BIT <= 7`.
--
> While the program works best when bytes/characters are octets and the number
of bits in a type is `sizeof(typ) << 3`, it will work correctly on 24-bit or
36-bit systems with 9 bits/byte, or systems where `sizeof(typ)` is 1 even for
`int` and so on. On such systems, it will only use `8 * sizeof(typ)` bits per
place. It does not work when `CHAR_BIT <= 7`.
<hr style="width:10%;text-align:left;margin-left:0">