diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-07-18 09:22:10 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2024-07-18 09:22:10 +0200 |
| commit | 958ee138748fae4371e453eb9b357f576abbe83e (patch) | |
| tree | 95e106dbc7cc5abe1665d2b66b340916c5bc860f /gcc/cp/tree.cc | |
| parent | 4b58697cecbd72fd7db5a0fcdf7af8deb3be2b14 (diff) | |
| download | gcc-958ee138748fae4371e453eb9b357f576abbe83e.zip gcc-958ee138748fae4371e453eb9b357f576abbe83e.tar.gz gcc-958ee138748fae4371e453eb9b357f576abbe83e.tar.bz2 | |
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.
Diffstat (limited to 'gcc/cp/tree.cc')
0 files changed, 0 insertions, 0 deletions