On Tue, May 10, 2022 at 02:58:49PM -0700, Palmer Dabbelt wrote: > On Thu, 05 May 2022 11:45:50 PDT (-0700), gcc-patches@gcc.gnu.org wrote: > > On Thu, May 05, 2022 at 06:33:20PM +0800, jiawei wrote: > > > Some compiler target like arm-linux\riscv\power\s390x\xtensa-gcc handle > > > char as unsigned char, then there are no warnings occur and got FAIL > > > cases. > > > Just change the type char into explicit signed char to keep the feature > > > consistency. > > > > > > gcc/testsuite/ChangeLog: > > > > > > * c-c++-common/Wconversion-1.c: Update type. > > > > Ok, and sorry for introducing this problem! > > So this is OK for trunk? Happy to commit it if you'd like, just wanted to > make sure as I'm not seeing it on trunk.
Yes, please go ahead. Marek
