aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Sayle <roger@nextmovesoftware.com>2022-05-05 08:30:27 -0400
committerRoger Sayle <roger@nextmovesoftware.com>2022-05-05 08:30:27 -0400
commit92fff39f06449f907d8781a5dcaad0e8b9743480 (patch)
tree56b6655297884d10b31159acece67bc3ca11e888
parent7ec6fed1e816d0671a076c59ea0ff88f736beaab (diff)
downloadgcc-92fff39f06449f907d8781a5dcaad0e8b9743480.zip
gcc-92fff39f06449f907d8781a5dcaad0e8b9743480.tar.gz
gcc-92fff39f06449f907d8781a5dcaad0e8b9743480.tar.bz2
[Committed] PR testsuite/105486: Use "signed char" in gcc.dg/pr102950.c
Although the automated regression testing scripts for powerpc64 appear to be somewhat garbled at the moment, they've correctly identified that my new test case for pr102950.c is failing on powerpc64, as char by default is unsigned on this target. This patch tweaks the new testcase by explicitly using "signed char" so that it's testing the intended EVRP behaviour portably. Committed as obvious. 2022-05-05 Roger Sayle <roger@nextmovesoftware.com> gcc/testsuite/ChangeLog PR testsuite/105486 * gcc.dg/pr102950.c: Use explicit "signed char" in test case.
-rw-r--r--gcc/testsuite/gcc.dg/pr102950.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/testsuite/gcc.dg/pr102950.c b/gcc/testsuite/gcc.dg/pr102950.c
index 0ab23bd..3175683 100644
--- a/gcc/testsuite/gcc.dg/pr102950.c
+++ b/gcc/testsuite/gcc.dg/pr102950.c
@@ -3,9 +3,9 @@
extern void link_error(void);
-static char a;
+static signed char a;
static short d(unsigned e) {
- char b;
+ signed char b;
short c;
a = b = e;
if (b)