<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>throwaway613834</author><text>To be fair, I&amp;#x27;ve also lost count of the number of times my compiler has compiled things correctly. ;)</text><parent_chain><item><author>cperciva</author><text>Sadly, I&amp;#x27;ve lost count of how many compiler bugs I&amp;#x27;ve tripped over through the years.  Often it&amp;#x27;s compiler crashes -- those are usually easy to get fixed, especially when (as tends to be the case with LLVM) they are caused by assertions failing -- but I&amp;#x27;ve also tripped over compiler &lt;i&gt;hangs&lt;/i&gt; (there&amp;#x27;s a variable in the tarsnap code with an utterly bogus volatile specifier in order to avoid the problematic optimization on some versions of llvm) and outright &lt;i&gt;miscompilations&lt;/i&gt; -- one of which has had several LLVM bug reports opened by different people over the years and remains unfixed.</text></item></parent_chain></comment><story><title>“It is never a compiler error”</title><url>https://blog.plover.com/2017/11/12/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>empath75</author><text>If you’re the kind of programmer who is likely to find compiler errors, you probably know who you are. For 99% of programmers, the chances that you have discovered one is small.</text><parent_chain><item><author>cperciva</author><text>Sadly, I&amp;#x27;ve lost count of how many compiler bugs I&amp;#x27;ve tripped over through the years.  Often it&amp;#x27;s compiler crashes -- those are usually easy to get fixed, especially when (as tends to be the case with LLVM) they are caused by assertions failing -- but I&amp;#x27;ve also tripped over compiler &lt;i&gt;hangs&lt;/i&gt; (there&amp;#x27;s a variable in the tarsnap code with an utterly bogus volatile specifier in order to avoid the problematic optimization on some versions of llvm) and outright &lt;i&gt;miscompilations&lt;/i&gt; -- one of which has had several LLVM bug reports opened by different people over the years and remains unfixed.</text></item></parent_chain></comment><story><title>“It is never a compiler error”</title><url>https://blog.plover.com/2017/11/12/</url></story>