So I filed a glibc bug with fedora to that effect:
https://bugzilla.redhat.com/show_bug.cgi?id=720176
In which Andreas Schwab points out (rightly or wrongly) that according
to the /proc/cpuinfo from the slice, the processor actually does not
support AVX. However, the "model name", "Intel(R) Xeon(R) CPU
E31230", is according to this a Sandy Bridge processor with AVX:
http://en.wikipedia.org/wiki/Sandy_Bridge#Server_processors
And while I do not have access to the hardware, the provider is very
unequivocal about the fact that these are Sandy Bridges, which
apparently include AVX.
So I am looking for a next step to take in debugging this. The kernel
used on the slice (nb, openVZ does not allow for rolling your own) is
2.6.32 built with gcc 4.1.2. I think this may be prior to AVX support
in the kernel and gcc, but the glibc is 2.13, which apparently includes
it.
Does anyone have any idea why I would get this identical backtrace, and
a failed reproducer test, on hardware which supposedly supports AVX
(but not according to the kernel in /proc/cpuinfo)?