Is it possibly to co-issue vector + scalar instructions on a R300?
Since I except the answer to that question to be yes, I'll give the followup question directly.
When can we expect that to be available in ARB_fragment_program?
It seems as it doesn't work now. I know that there aren't any explicit support in that extension, but there's no reason to not detect possible co-issues in the drivers, and generate the co-issue-operations automatically.
And what operations exactly can be co-issued? Restrictions for operators and operands. (Except for the obvious: one instruction may only write to .rgb components, the other only to .a component.)
[Edit]
Got a confirmed 'Yes' to the first question even before I posted this message. (Humus being in non-causal mode?
)
Since I except the answer to that question to be yes, I'll give the followup question directly.
When can we expect that to be available in ARB_fragment_program?
It seems as it doesn't work now. I know that there aren't any explicit support in that extension, but there's no reason to not detect possible co-issues in the drivers, and generate the co-issue-operations automatically.
And what operations exactly can be co-issued? Restrictions for operators and operands. (Except for the obvious: one instruction may only write to .rgb components, the other only to .a component.)
[Edit]
Got a confirmed 'Yes' to the first question even before I posted this message. (Humus being in non-causal mode?
)