On Tue, Feb 05, 2019 at 05:04:03PM +0100, Jakub Jelinek wrote: > On Sat, Feb 02, 2019 at 05:09:37PM -0600, Segher Boessenkool wrote: > > > 2019-02-01 Kelvin Nilsen <kel...@gcc.gnu.org> > > > > > > * gcc.target/powerpc/vec-extract-slong-1.c: Require p8 execution > > > hardware. > > > * gcc.target/powerpc/vec-extract-schar-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-sint128-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-sshort-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-ulong-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-uchar-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-sint-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-uint128-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-ushort-1.c: Likewise. > > > * gcc.target/powerpc/vec-extract-uint-1.c: Likewise. > > I don't see how the vec-extract-?int128-1.c tests could pass on big endian > power8 with -m32, __int128 type is only supported for 64-bit targets.
This is fine, okay for trunk, thanks! Segher > 2019-02-05 Jakub Jelinek <ja...@redhat.com> > > * gcc.target/powerpc/vec-extract-sint128-1.c: Require int128 effective > target. > * gcc.target/powerpc/vec-extract-uint128-1.c: Likewise.
