Created attachment 138964 [details]
piglit test that triggers the faulty behaviour
The attached piglit test will run through in release mode, because sb bails out in the post_scheduler:
##post_scheduler: unscheduled pending instructions :MOV R6.x.1F, 0.5|3f000000
MOV R5.x.1F, 0|00000000
MOV R3.x.1F, 1|3f800000
sb: error (1) in the post_scheduler pass.
sb: using unoptimized bytecode...
Obviously it would be preferable if sb would generate proper code instead.
Also in debug mode an assertion will fail at this point.
It is another incarnation of #103142, but I think it is better to open this as a new bug.
A patch fixing this has been submitted to the ML:
This.. seems to have been fixed, I think?
My own case at least does.
Yes, fixed with eebb65258d15af2b2fc50d3b64b5d2eafbffcb47
r600/sb: give the scheduler more margin to find valid instructions groups