<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@allafarce" class="u-url mention">@<span>allafarce</span></a></span> I&#39;ve come to realize that it&#39;s not actually a technical remark, it&#39;s actually a political one. Basically it&#39;s a statement of tribal identity (especially when preceded by &quot;just&quot;).</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.nu/@richcarl" class="u-url mention">@<span>richcarl</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@DRMacIver" class="u-url mention">@<span>DRMacIver</span></a></span> <br />I don&#39;t think auto*complete* is much more useful. Prompts like mine involve *quantification*: on *every* round, do X. It doesn&#39;t just do X; faithfully executes for-all X (for several rounds anyway). I don&#39;t know any &quot;autocomplete&quot; that behaves like that.</p>

<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@dlharmon" class="u-url mention">@<span>dlharmon</span></a></span> I suppose more accurately what I want to build would be described as &quot;timing check during synthesis&quot;</p><p>rather than merely considering CDCs it uses a more abstract model than P&amp;R to conservatively avoid violations</p>

<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention">@<span>0xabad1dea</span></a></span> suffering</p>

<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@dlharmon" class="u-url mention">@<span>dlharmon</span></a></span> sure they would, all toplevel inputs would be considered asynchronous to any clock in the design unless marked otherwise</p>

<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@nrc" class="u-url mention">@<span>nrc</span></a></span> you can take a look at Rubocop or mbj&#39;s Unparser to see how they use it</p><p>apparently my AST format became somewhat of a de facto standard in the decade since, which is wild.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> Same, I&#39;ve tried and failed to create metastabilty or at least something I could say for certain was. Perhaps the ~18 ps resolution on 7-series MMCM fine phase shift wasn&#39;t enough. I&#39;d have thought jitter would have taken care of the rest. Maybe my clock was too low and the metastability resolved before the 2nd stage FFs could sample it.</p><p>I should try it again with a DDS (~fs res.), like 700 MHz clocks.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@dlharmon" class="u-url mention">@<span>dlharmon</span></a></span> CDC checks won&#39;t help if the input is coming from off chip and inherently async.</p>

<p><span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@dlharmon" class="u-url mention">@<span>dlharmon</span></a></span> we really need to add a built-in CDC checker to Amaranth...</p>