Richard Henderson wrote: > On 01/25/2016 05:28 AM, Christophe Lyon wrote: > > After this, I'm seeing this test now FAILs: > > gcc.target/aarch64/ccmp_1.c scan-assembler adds\t > > That test case is badly written. In addition to that one, several of the > other > failures that I see within that file are simply equally optimal alternative > choices for the compiler. The file needs to be split up and simpler more > directed tests written.
The test case was written specifically to emit 'adds' as that is the optimal sequence. It is a regression caused by wrapping the immediate in a unspec which disables costing of all CCMPs... I have a patch for this. The zero issue is due to the testcase assuming GCC emits '0' and 'wzr' correctly - it was based on a very old patch that emits the correct zero for compares that hasn't been OK'd yet. And the failure to emit an fccmp is due to a recent fix to NaN handling in compares, so that testcase now needs -ffinite-math-only. Wilco
