2 ms·
It's closer than it's ever been! The rough plan: * move asm! to llvm_asm. https://github.com/rust-lang/rust/pull/68404 https://github.com/rust-lang/rust/pull/6
by steveklabnik 7y ago
It's closer than it's ever been! The rough plan:
* move asm! to llvm_asm. https://github.com/rust-lang/rust/pull/68404 https://github.com/rust-lang/rust/pull/68404
* implement the actual asm! we want to stabilize: https://github.com/rust-lang/rfcs/pull/2873 https://github.com/rust-lang/rfcs/pull/2873
* stabilize it
- pavehawk2007 7y agoI stand corrected! Thanks for the info!
- steveklabnik 7y agoIt's all good. I think that was the prevailing sentiment for years, but Amanieu put in the work, and things are looking bright. It hasn't been accepted yet, of course, so anything could happen. But stuff is moving in that direction, it seems.
- jeffdavis 7y agoCool! Curious why not WASM also? I have no use case for that, just asking.
- steveklabnik 7y agoSorry, I'm not entirely sure what you're asking?
- monadic2 7y agoPerhaps why there is no wasm equivalent directive? Just a guess.
- skavi 7y agoThey are probably asking why WASM (probably in .wat format) is not an option alongside x86/x86-64, ARM, AArch64, and RISC-V.
- steveklabnik 7y agoRelying to myself rather than replying to three people: this would be a good question on the RFC, but I would imagine that this would be possible, just not super useful. Usually inline asm is useful for doing stuff you cannot do in the higher level language, but wasm doesn’t have anything like that currently. I would imagine that it would be a fairly straightforward extension though.