Re: [PATCH] Fix handling of VEC_COND_EXPR trap tests [PR100284]

On April 27, 2021 5:22:56 PM GMT+02:00, Richard Sandiford wrote: >Richard Biener writes: >> On April 27, 2021 5:12:35 PM GMT+02:00, Richard Sandiford > wrote: >>>Now that VEC_COND_EXPR has normal unnested operands, >>>operation_could_trap_p can treat it like any other expression. >>> >>>This fix

Re: [PATCH] Fix handling of VEC_COND_EXPR trap tests [PR100284]

Richard Biener writes: > On April 27, 2021 5:12:35 PM GMT+02:00, Richard Sandiford > wrote: >>Now that VEC_COND_EXPR has normal unnested operands, >>operation_could_trap_p can treat it like any other expression. >> >>This fixes many testsuite ICEs for SVE, but it turns out that none >>of the tes

Re: [PATCH] Fix handling of VEC_COND_EXPR trap tests [PR100284]

On April 27, 2021 5:12:35 PM GMT+02:00, Richard Sandiford wrote: >Now that VEC_COND_EXPR has normal unnested operands, >operation_could_trap_p can treat it like any other expression. > >This fixes many testsuite ICEs for SVE, but it turns out that none >of the tests in gcc.target/aarch64/sve were

[PATCH] Fix handling of VEC_COND_EXPR trap tests [PR100284]

Now that VEC_COND_EXPR has normal unnested operands, operation_could_trap_p can treat it like any other expression. This fixes many testsuite ICEs for SVE, but it turns out that none of the tests in gcc.target/aarch64/sve were affected. Anyone testing on non-SVE aarch64 therefore wouldn't have se