Re: [PATCH] testsuite: Fix pr108574-3.c failed in arch where sign defaults to unsigned.

2023-01-31 Thread Richard Biener via Gcc-patches
On Tue, 31 Jan 2023, Richard Biener wrote: > On Tue, 31 Jan 2023, Xianmiao Qu wrote: > > > In the architecture where sign defaults to unsigned, the 'f' will be zero > > extended to int type in the expression 'd = ~(f & ~2880764155)', then the > > 'd' will become -1 wich cause the case to fail. >

Re: [PATCH] testsuite: Fix pr108574-3.c failed in arch where sign defaults to unsigned.

2023-01-30 Thread Richard Biener via Gcc-patches
On Tue, 31 Jan 2023, Xianmiao Qu wrote: > In the architecture where sign defaults to unsigned, the 'f' will be zero > extended to int type in the expression 'd = ~(f & ~2880764155)', then the > 'd' will become -1 wich cause the case to fail. > So it's ok for the architectures where sign defaults

[PATCH] testsuite: Fix pr108574-3.c failed in arch where sign defaults to unsigned.

2023-01-30 Thread Xianmiao Qu via Gcc-patches
In the architecture where sign defaults to unsigned, the 'f' will be zero extended to int type in the expression 'd = ~(f & ~2880764155)', then the 'd' will become -1 wich cause the case to fail. So it's ok for the architectures where sign defaults to signed like x86, but failed for the