<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> We fairly regularly saturate a 72-core machine with shrinkray, which still blows my mind -- and is a massive productivity boost!</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@shriramk" class="u-url mention">@<span>shriramk</span></a></span> I&#39;m not a local, but based on my limited experience (a dozen visits over a decade or so), that is a safe bet everywhere in Quebec, but not in Montreal</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@DRMacIver" class="u-url mention">@<span>DRMacIver</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@ltratt" class="u-url mention">@<span>ltratt</span></a></span> ohhhh, I&#39;ve been struggling with C-Reduce on my workloads, I&#39;ll give shrinkray a try!</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@gamingonlinux" class="u-url mention">@<span>gamingonlinux</span></a></span> MangoHUD is the best system monitor overlay out there, regardless of OS. Whenever I have to use Windows to play a game due to garbage anticheat I miss it dearly. RivaTuner Statistics Server is just nowhere near as good.</p><p>I just wish MangoHud would auto-configure whatever is necessary to report CPU power usage appropriately.</p><p>FEX emulator statistics is a great addition for gaming on ARM!</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@ltratt" class="u-url mention">@<span>ltratt</span></a></span> I suspect a lot of why it&#39;s not better known is just that I&#39;ve not advertised it very well. I&#39;m not really sure how other than word of mouth - the &quot;customer base&quot; for this sort of tool isn&#39;t super large, and for a lot of them C-reduce is plenty good enough.</p>

<p>For a little while we&#39;ve been using Shrinkray (<a href="https://github.com/DRMacIver/shrinkray" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="">github.com/DRMacIver/shrinkray</span><span class="invisible"></span></a>) for these purposes, and I&#39;m astonished it&#39;s not better known. It seems to improve on the older reducers in every way!</p><p>Shrinkray has very sensible rules that apply well to languages it has no specific knowledge of -- we make a *lot* of use of this and it&#39;s brilliant! -- and it scales near-linearly to the number of cores. If you need a reducer, I highly recommend it! Thanks <span class="h-card" translate="no"><a href="https://mastodon.social/@DRMacIver" class="u-url mention">@<span>DRMacIver</span></a></span>!</p>

<p>Working on compilers inevitably leads to situations where massive inputs cause bugs. The problem is that &quot;massive&quot; from a human perspective starts at about 20 lines of code. What can one do to recover sanity?</p><p>&quot;Test-case reducers&quot; are the answer: they chop away the input using an &quot;interesting&quot; test, making sure that the bug you care about is still retained. It&#39;s not uncommon for 99+% of an input to be unnecessary to trigger the bug you care about.</p>

<p>After a busy morning of unfurling and rigging work, we have sailed off our anchor and are making way towards Sint Maarten.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@shriramk" class="u-url mention">@<span>shriramk</span></a></span> Are they all ASCII characters / in the basic multilingual plane / non-composites? I could see this easily arising from how they count “character”.</p>