Any other comments or is it good to go in? Since this is just a one line fix.
On Tue, Oct 6, 2026 at 4:32 PM jeevitha <[email protected]> wrote: > > > On 02/10/26 9:43 pm, Manjunath S Matti wrote: > > Add the int128 effective-target requirement, the test then > > becomes UNSUPPORTED for -m32 and is unchanged for -m64 on both > > endiannesses. > > > > Just a small wording change: use "int128 effective-target check" > instead of "int128 effective-target requirement"? > > Other than this small change, it looks correct. > > Thanks, > Jeevitha. > > > Tested on powerpc64-linux-gnu (-m64 and -m32) and > > powerpc64le-linux-gnu. > > > > 2026-10-02 Manjunath Matti <[email protected]> > > > > gcc/testsuite/ > > PR target/127278 > > * gcc.target/powerpc/vec-msumc.c: Add int128 > > effective-target. > > > > diff --git a/gcc/testsuite/gcc.target/powerpc/vec-msumc.c > b/gcc/testsuite/gcc.target/powerpc/vec-msumc.c > > index 524a2225c6c..c9db899c2f9 100644 > > --- a/gcc/testsuite/gcc.target/powerpc/vec-msumc.c > > +++ b/gcc/testsuite/gcc.target/powerpc/vec-msumc.c > > @@ -1,4 +1,5 @@ > > /* { dg-do run { target { power10_hw } } } */ > > +/* { dg-require-effective-target int128 } */ > > /* { dg-require-effective-target power10_ok } */ > > /* { dg-options "-mdejagnu-cpu=power10 -O2" } */ > > #include <altivec.h> > >
