aboutsummaryrefslogtreecommitdiff
path: root/gcc/range-op-float.cc
diff options
context:
space:
mode:
authorAndrew Pinski <apinski@marvell.com>2023-07-25 21:50:33 +0000
committerAndrew Pinski <apinski@marvell.com>2023-07-25 14:56:23 -0700
commit67357270772b9131f1780267485c9eba0331bd6f (patch)
treeb82d44b2656292d936317b3d6c1dfaed0c85376b /gcc/range-op-float.cc
parent099d40ba776c0722888c3aa40c87c818892e04bb (diff)
downloadgcc-67357270772b9131f1780267485c9eba0331bd6f.zip
gcc-67357270772b9131f1780267485c9eba0331bd6f.tar.gz
gcc-67357270772b9131f1780267485c9eba0331bd6f.tar.bz2
Fix 110803: use of plain char instead of signed char
So the problem here is that plain char can either be signed or unsigned depending on the target (powerpc and aarch64 are unsigned while most other targets are signed). So the testcase gcc.c-torture/execute/pr109986.c was assuming plain char was signed char which is wrong so it is better to just change the `char` to be `signed char`. Note gcc.c-torture/execute/pr109986.c includes gcc.dg/tree-ssa/pr109986.c where the plain char was being used. Committed as obvious after a quick test to make sure gcc.c-torture/execute/pr109986.c now passes and gcc.dg/tree-ssa/pr109986.c still passes. gcc/testsuite/ChangeLog: PR testsuite/110803 * gcc.dg/tree-ssa/pr109986.c: Change plain char to be `signed char`.
Diffstat (limited to 'gcc/range-op-float.cc')
0 files changed, 0 insertions, 0 deletions