Whole-known-network
<p>Horripilant is a chilling incremental dungeon crawl through the horrors of a forgotten underworld <a href="https://www.gamingonlinux.com/2025/04/horripilant-is-a-chilling-incremental-dungeon-crawl-through-the-horrors-of-a-forgotten-underworld/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">gamingonlinux.com/2025/04/horr</span><span class="invisible">ipilant-is-a-chilling-incremental-dungeon-crawl-through-the-horrors-of-a-forgotten-underworld/</span></a></p><p><a href="https://mastodon.social/tags/Horripilant" class="mention hashtag" rel="tag">#<span>Horripilant</span></a> <a href="https://mastodon.social/tags/IndieGames" class="mention hashtag" rel="tag">#<span>IndieGames</span></a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="tag">#<span>Linux</span></a> <a href="https://mastodon.social/tags/SteamDeck" class="mention hashtag" rel="tag">#<span>SteamDeck</span></a></p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> sorry, I misunderstood the context</p>
<p><span class="h-card" translate="no"><a href="https://masto.ai/@skandhurkat" class="u-url mention">@<span>skandhurkat</span></a></span> this is completely irrelevant</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> if it is a shift where both the value and the shift amount are in registers, both quantities will have the same number of bits. If the shift amount is an immediate, then the number of bits available for the shift amount will match whatever the bit width for immediates is in that ISA, just to keep the decode easy.</p>
<p>whose fucking idea was it to require the shift amount to have the same width as the value to be shifted? is this purposefully designed to torture compiler developers??</p>
<p>every time i have to interact with SMT solvers it leaves me incandescently angry in a way little other tooling does. would it fucking kill you to allow zero length bitvectors? did you take inspiration from verilog??</p>
<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> Ah, thank you!<br />I was confused by later comments in the thread.</p>
<p><span class="h-card" translate="no"><a href="https://chaos.social/@soc" class="u-url mention">@<span>soc</span></a></span> no? SMT-LIB is its own language, vaguely lispy in nature</p>
<p>if SMT-LIB was designed for actually useful applications it would have had a function to replace a chunk of a bitvector with something else, instead of forcing you to do a {let binder, extract, extract, concat} dance and hope whatever you're using to emit code is flexible enough that you can actually get the let binder to work (or you end up with quadratic growth of SMT-LIB terms)</p>