Hi,
Yeah, that's because of the very limited analysis we do in the backend to
detect such cases. In fact
we probably would want to have an OSC break in many of them as well.
For me the testcase appears to work with -O2 on all the -march levels. I think
-O2 would be
preferred because that's wh
On 4/16/21 3:59 PM, Robin Dapp wrote:
> Hi,
>
> checking for an osc break is somewhat brittle especially with many
> passes potentially introducing new insns and moving them around.
> Therefore, only run the test with -O1 -fschedule-insns in order to limit
> the influence of other passes.
Yeah, t
Hi,
checking for an osc break is somewhat brittle especially with many
passes potentially introducing new insns and moving them around.
Therefore, only run the test with -O1 -fschedule-insns in order to limit
the influence of other passes.
Is it OK?
Regards
Robin
--
gcc/testsuite/ChangeLog:
