Comment 3 for bug 937864

On Tue, Feb 21, 2012 at 03:52:29PM -0000, Ulrich Weigand wrote:
>Maybe I'm missing something, but as I understand those *are* valid VFPv3
>(even VFPv2) instructions, not just NEON instructions ...

Oh, hmmm...

Maybe I'm being too quick to complain for *these* specific
instructions. This came out of a discussion on #debian-arm a few weeks
back, related to the build failure referenced in

  https://buildd.debian.org/status/fetch.php?pkg=pytables&arch=armhf&ver=2.3.1-1&stamp=1327297899

Oh, hmmm. Looking at the irc log for that discussion, the user in
question is pointing at another instruction instead:

2012-01-23 22:14 GMT< yoh> Program received signal SIGILL, Illegal instruction.
2012-01-23 22:14 GMT< yoh> conv_float64_timeval32 (base=<optimized out>, byteoffset=<optimized out>, bytestride=<optimized out>, nrecords=49932, nelements=2, sense=0) at src/typeconv.c:72
2012-01-23 22:14 GMT< yoh> 72 | (lround((*fieldbase - (int)(*fieldbase)) * 1e+6)
2012-01-23 22:16 GMT< yoh> I think that is the one /home/yoh/pytables/build/temp.linux-armv7l-2.6/src/typeconv.o
2012-01-23 22:17 GMT< yoh> disassemble gives => 0x2bc6950a <+170>: vcvt.s32.f64 s14, d8

I was too quick at jumping on vldr without thinking about VFPv3.

Cheers,
--
Steve McIntyre <email address hidden>
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs