https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119629
--- Comment #9 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #8)
> Both messages seem valid, so I think we can probably modify the test case to
> look for both error messages.
This fixes the test case:
diff --git a/gcc/testsuite/gcc.target/powerpc/byte-in-set-2.c
b/gcc/testsuite/gcc.target/powerpc/byte-in-set-2.c
index 4c676ba356d..ae001d21edc 100644
--- a/gcc/testsuite/gcc.target/powerpc/byte-in-set-2.c
+++ b/gcc/testsuite/gcc.target/powerpc/byte-in-set-2.c
@@ -10,5 +10,8 @@
int
test_byte_in_set (unsigned char b, unsigned long long set_members)
{
- return __builtin_byte_in_set (b, set_members); /* { dg-error
"'__builtin_scalar_byte_in_set' requires the" } */
+ /* The built-in machinery gives us two different error messages depending
+ on if we compiled using -m32 -mno-powerpc64 or -m32 -mpowerpc64.
+ Look for both error messages. */
+ return __builtin_byte_in_set (b, set_members); /* { dg-error
"'__builtin_scalar_byte_in_set' (requires the|is not supported)" } */
}
