|
From: Philippe W. <phi...@sk...> - 2017-05-20 15:03:26
|
On Thu, 2017-05-18 at 00:40 +0200, Ivo Raisr wrote: > 2017-05-17 23:09 GMT+02:00 Philippe Waroquiers <phi...@sk...>: > > On Wed, 2017-05-17 at 23:03 +0200, Philippe Waroquiers wrote: > >> Not too clear to me what are these adcx* instructions, and if they > >> are supposed to be supported according to the configure test, which > >> checks vmovupd and vaddpd instructions. > > As I understand, adcx instruction is available if adx extension > > is supported. > > > > On my desktop (where the test compile) adx is in /proc/cpuinfo. > > > > But on gcc20, there is no such adx flag. > > > > I imagine we need a specific configure test for BUILD_ADX_TESTS? > > > > What do you think? > > Yes, that would be probably the most sane way how to check binutils capabilities > in this case. In revision 16401, I committed a change that unbreaks the build on gcc20 kind of systems (using a BUILD_ADX_TESTS). Note however that adx capable systems are however reported by V as being non adx capable. I guess a cleaner/full fix/full support for adx implies to change the synthetic cpu hwcaps provided by V (as cpuid reports a non adx capable system) Philippe |