3 ms·
Nice overview, it might be worth mentioning that Emscripten isn't a tier 1 platform[1]. We've seen some asserts thrown in LLVM when building debug but go away w
by vvanders 9y ago
Nice overview, it might be worth mentioning that Emscripten isn't a tier 1 platform[1]. We've seen some asserts thrown in LLVM when building debug but go away when build release.
I've been trying to isolate it down to a reproducible sample but haven't nailed down exactly what's causing it yet.
Even with that issue it's been great to work with. I find myself so much more productive with Rust compared to C/C++.
[1] https://forge.rust-lang.org/platform-support.html https://forge.rust-lang.org/platform-support.html
- dbaupp 9y agoIf you've got something large that asserts consistently, you could consider throwing some CPU time at it via creduce. It is designed for C, but Rust is close enough that a lot of its heuristics still work just fine. Alternatively, since setting up/running creduce can be bit fiddly, if the code is open source, I suspect that someone would do it for you if you filed a bug against Rust pointing to an exact commit that demonstrates the problem with `cargo build --target=...` (or xargo) and requested/suggested creduce.
- vvanders 9y agoThanks, I'll give that a shot. Unfortunately the code which is why I was trying to pair it down to a simple sample.