Ben Kimock

Can you explain how this issue is related to https://github.com/rust-lang/rust/issues/119306? We already explained there that Rust supports Android targets, we just don't automatically build releases that support termux as a...

Rust supports building executables that run on Android/termux. We just do not distribute compilers that run on Android/termux. You can run the compiler on another platform and using `--target` have...

It's hard to imagine the attribute regressing runtime performance, but yes it can massively regress compile times. The original case study for that is `hashbrown` which used to put it...

> Miri tests don't succeed on x86 either. Are you sure about that? Miri has decent x86_64 shims as of rather recently; with default flags the searcher fails to build...

I agree with that completely. Miri doesn't have much if any neon support and would need a lot for this use case.

Ah; the reason tests don't work on Miri + x86 by default is that aho-corasick tries to do runtime CPU feature detection (in `teddy`) which in Miri doesn't get you...

> I think my underlying question is, why can't Miri let runtime CPU feature detection actually inspect the CPU features of the host? Like, what is the blocker? Miri tries...

Well, nothing is out of the question. `--no-capture` does produce colors which is good but it looks like this is the equivalent of `--nocapture` which is not so great. A...

I think `CARGO_TERM_COLOR` doesn't work with `cargo-miri` because `cargo-miri` isn't actually Cargo. Argh, maybe this is a good reason to straighten out that whole situation.

I removed my vim config before reporting this. If you can't reproduce this, I can investigate further to see if there's something about my system elsewhere that's driving this, but...