We have a lot of open issues about the various bugs in
llvm_asm!. At the moment there is no plan to fix these, we are instead encouraging people to migrate to the new
asm! instead. Should we go ahead and close most of these issues if they do not apply to the new
I figure we can close about 40 issues.
Wouldn't it make more sense to wait until the new
asm! lands on nightly? Until then users of
llvm_asm! couldn't migrate and check if their issue is still relevant with the new
It has landed
It's on master now but I don't a nightly with it is released yet.
Anyway probably it's better to wait a little to allow ppl to try the new asm first
Most issues are LLVM crashes and rustc ICEs, so they can probably all be closed as wontfix immediately (unless
asm! has the same bug)
Yeah, it would be nice to translate all the issues into the new
asm! (if possible) and verify that they don't reproduce.
Perhaps some of them are LLVM issues independent from our asm flavor.
I would support that policy -- translate and check. If there's an easy to use guide for how to do so (we should definitely have one!) then I imagine we could largely get the community to provide the translations, too.
I do think we should have a policy going forward of closing llvm_asm! issues that get filed, and asking filer(s) to try with asm! and file new issues as needed.
I definitely think that trying to enlist community to do that translation would be better than having @Amanieu try to do it all by themselves...
...I also think a plausible strategy might to leave a comment on each issue, encouraging the OP or others to port it to the new
asm!, and after some amoutn of time, close the rest
that + publish a list somewhere of the issues and try to get eyeballs
Actually @Amanieu I think an
Inside Rust! blog post about the new
asm! syntax would be a nice thing to do
It's not such a big deal, most of the issues are caused by passing invalid types to
asm!. These are all rejected by the new
asm! type checking.
and at the end there could be a
that encourages people to try it out, give feedback, and/or do any kind of rote work we want
ok, regardless I think it'd be great to have a blog post touting the new feature :)
or maybe @Josh Triplett wants to do it
I'd probably just crib from the RFC
i.e., include a few examples and things
the text was already pretty darn readable
I would be quite happy to write such a blog post.
I can help review the blog post if you like.
I plan to include a simple hello world example, but if you have an example of using asm for acceleration, that might help as well.