On Sat, Jul 20, 2019 at 12:33:16PM -0400, David Edelsohn wrote:
> On Sat, Jul 20, 2019 at 2:39 AM Gerald Pfeifer wrote:
> >
> > I have seen an increasing number of reports of GCC failing to
> > build with clang on powerpc (on FreeBSD, though that's probably
> > immaterial).
> >
> > Turns out that
On Sat, Jul 20, 2019 at 2:39 AM Gerald Pfeifer wrote:
>
> I have seen an increasing number of reports of GCC failing to
> build with clang on powerpc (on FreeBSD, though that's probably
> immaterial).
>
> Turns out that clang has vec_step as a reserved word on powerpc
> with AltiVec.
>
> We OTOH u
Gerald Pfeifer writes:
> I have seen an increasing number of reports of GCC failing to
> build with clang on powerpc (on FreeBSD, though that's probably
> immaterial).
>
> Turns out that clang has vec_step as a reserved word on powerpc
> with AltiVec.
>
> We OTOH use vec_step s as a variable name
I have seen an increasing number of reports of GCC failing to
build with clang on powerpc (on FreeBSD, though that's probably
immaterial).
Turns out that clang has vec_step as a reserved word on powerpc
with AltiVec.
We OTOH use vec_step s as a variable name in gcc/tree-vect-loop.c.
The best ap
