<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://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> 68 octets if a vlan tag is present. <a href="https://www.cisco.com/c/en/us/support/docs/lan-switching/8021q/17056-741-4.html" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">cisco.com/c/en/us/support/docs</span><span class="invisible">/lan-switching/8021q/17056-741-4.html</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> My read on this is that the FCS is included within the 64 byte minimum frame size.</p><p>802.3-2012 4.2.3.3</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> yes, 64 octets including src/dest MAC, 802.1q tag if present, ethertype/length, frame body, and FCS.</p><p>Preamble/SFD and interframe gap do not count towards the 64</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> alignment: i think it works like this:</p><p>i32.load align=2</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> block example: <a href="https://developer.mozilla.org/en-US/docs/WebAssembly/Reference/Control_flow/block" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">developer.mozilla.org/en-US/do</span><span class="invisible">cs/WebAssembly/Reference/Control_flow/block</span></a></p><p>querying stack depth: no, you&#39;re not allowed to do anything that would make stack depth dynamic, therefore there is no need to have an operation to query it</p>

<p>networking folks: the minimum Ethernet frame size is 64 octets, right? does that include the FCS?</p>

<p>By the way if anyone has an easy way to point me to any of the following it would be much appreciated</p><p>- An example of the (block) syntax in textual wasm<br />- An &quot;alignment&quot; is described in &quot;memarg&quot; in the spec, but this shows up nowhere in the textual wasm examples I find. Is this implicit in the use of `i32.` instructions?<br />- Is there a way to query the current wasm stack depth?</p>

<p>OK so</p><p>I&#39;m struggling with this week due to many issues that feel to me artificial. I don&#39;t like how this spec is written. I don&#39;t like a lot of the decisions</p><p>Buuut *sigh*</p><p>I guess I got the Good Idea out of the wasm spec I was hoping to find when I picked it. I was feeling like this S-expression form didn&#39;t &quot;feel like&quot; a LISP. And then I found this bit in the PDF spec. Using a syntax reordering trick to represent a Forth in LISP style. That&#39;s *saying this as if miserable* really smart actually</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> this is the simplest thing you can do to accomplish this task in plain wasm, yes</p>