gcc-9-20190720 is now available

2019-07-20 Thread gccadmin
Snapshot gcc-9-20190720 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/9-20190720/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-9

Re: Renaming vec_step in tree-vect-loop.c (to fix build on powerpc/clang)

2019-07-20 Thread Segher Boessenkool
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

Re: Renaming vec_step in tree-vect-loop.c (to fix build on powerpc/clang)

2019-07-20 Thread David Edelsohn
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

Re: Renaming vec_step in tree-vect-loop.c (to fix build on powerpc/clang)

2019-07-20 Thread Richard Sandiford
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