Re: GCC 7 on ppc64le does not recognize vec_xl_be?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Nov 16, 2019 at 6:25 AM Segher Boessenkool
<segher@xxxxxxxxxxxxxxxxxxx> wrote:
>
> Hi Jeffrey,
>
> On Fri, Nov 15, 2019 at 08:05:57PM -0500, Jeffrey Walton wrote:
> >     g++ -DNDEBUG -g2 -O3 -mcpu=power9 -maltivec -c ppc_power9.cpp
>
> You forgot -Wall -Wextra, or at the very least -Wall.  It probably will
> help you find this problem., too.

OK, thanks.

I have a comprehensive test script that does things like -Wall
-Wextra. It takes 4 to 6 hours to run. It is not suitable for Travis,
though.

GCC135 is Power9, but it only has GCC 4.8 and at12 compilers. The at12
compiler does not warn of anything of interest with elevated warnings.
Just the standard unknown pragmas due to some OMP code paths.

Do you know where to find a Power9 machine with GCC 7?

> -g2 is the default, and -maltivec is implied by -mcpu=power9.
>
> Why do you disable assertions (-DNDEBUG)?
>
> >     ppc_simd.h: In function ‘uint32x4_p VecLoadBE(const byte*)’:
> >     ppc_simd.h:466:24: error: ‘vec_xl_be’ was not declared in this scope
> >          return (uint32x4_p)vec_xl_be(0, CONST_V8_CAST(src));
>
> You didn't #include <altivec.h> in this scope, or you have undefined
> __VSX__, or undefined something else; it is impossible for us to tell.

Yeah, I can't get a terminal so I can't do things like g++ -dM -E on
Travis to see what is going on.

Jeff




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux