testsuite: Fix up builtin-clear-padding-3.c for -funsigned-char

As reported on gcc-regression, this test FAILs on aarch64, but my
r15-2090 change didn't change anything on the generated assembly,
just added the forgotten dg-do run directive to the test, so the
test has been failing forever, just we didn't know it.

I can actually reproduce it on x86_64 with -funsigned-char too,
s2.b.a has int type and -1 is stored to it, so we should compare
it against -1 rather than (char) -1; the latter is appropriate for
testing char fields into which we've stored -1.

2024-07-18  Jakub Jelinek  <jakub@redhat.com>

	* c-c++-common/torture/builtin-clear-padding-3.c (main): Compare
	s2.b.a against -1 rather than (char) -1.

(cherry picked from commit 958ee13874)
This commit is contained in:
Jakub Jelinek
2024-07-18 09:22:10 +02:00
committed by Jakub Jelinek
parent f443de1de3
commit 39f89e0daf

View File

@@ -34,7 +34,7 @@ main ()
foo (&s1, 0);
foo (&s2, 0);
__builtin_clear_padding (&s2);
if (s2.b.a != (char) -1)
if (s2.b.a != -1)
__builtin_abort ();
__builtin_clear_padding (&s2.b.a);
__builtin_memset (&s2.b.a + 1, 0, sizeof (union U) - sizeof (s2.b.a));