From: Ralf Jung Date: Fri, 13 Mar 2026 08:23:32 +0000 (+0100) Subject: link to reddit thread X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/de23ecdef4d5ffdf3d168695d8dd97670b0446ec?ds=inline;hp=ef26e321391b25191bcda8313fcb9d51b287f882 link to reddit thread --- diff --git a/personal/_posts/2026-03-13-inline-asm.md b/personal/_posts/2026-03-13-inline-asm.md index 5e9a93b..ea5ef48 100644 --- a/personal/_posts/2026-03-13-inline-asm.md +++ b/personal/_posts/2026-03-13-inline-asm.md @@ -1,6 +1,7 @@ --- title: "How to use storytelling to fit inline assembly into Rust" categories: rust +reddit: /rust/comments/1rshm93/how_to_use_storytelling_to_fit_inline_assembly/ --- The Rust Abstract Machine is full of [wonderful oddities]({% post_url 2020-12-14-provenance %}) that do not exist on the [actual hardware]({% post_url 2019-07-14-uninit %}). @@ -290,6 +291,6 @@ but as the `innocent` example at the top of the post shows, we cannot leave inli The storytelling approach is my proposal for filling that gap. I plan to eventually suggest it as the official rules for inline assembly. But before I do that, I'd like to be more confident that this approach really can handle most real-world scenarios. -If you have examples of assembly blocks that cannot be explained with storytelling, but that you are convinced are correct and hence should be supported, please let us know, either in the immediate discussion for this blog post or (if you are reading this later) in the [t-opsem Zulip channel](https://rust-lang.zulipchat.com/#narrow/channel/136281-t-opsem). +If you have examples of assembly blocks that cannot be explained with storytelling, but that you are convinced are correct and hence should be supported, please let us know, either in the immediate [discussion](https://www.reddit.com/r/rust/comments/1rshm93/how_to_use_storytelling_to_fit_inline_assembly/) for this blog post or (if you are reading this later) in the [t-opsem Zulip channel](https://rust-lang.zulipchat.com/#narrow/channel/136281-t-opsem). #### Footnotes