The problem is due to a non-alignment issue as you previously suggested. Suppressing it via the build configuration change is a procedural matter: work to find the root problem and a real solution continues nonetheless.
On Nov 4, 2015, at 7:46 PM, Martin Buchholz <marti...@google.com> wrote: > OK, I looked a little closer. > > We need to actually understand this crash, and create a small repro recipe. > > It's not at all obvious what the purpose of those methods in Bits.java and > Bits.c is - they apparently always byte-swap, but that is very surprising > from their names, e.g. copyToIntArray. Give those methods some javadoc! Maybe > the crash comes from type punning int* and float* ? We shouldn't suppress the > crash unless we can prove it's actually a compiler bug. Why do these methods > take Object instead of e.g. int[] as parameters?
