ARB_shader_ballot Posted For RadeonSI, Can Be Used For AZDO Techniques

[phoronix]

Phoronix: ARB_shader_ballot Posted For RadeonSI, Can Be Used For AZDO Techniques

The latest RadeonSI OpenGL extension work done by AMD developer Nicolai Hähnle is on the useful ARB_shader_ballot extension...

http://www.phoronix.com/scan.php?page=news_item&px=ARB-Shader-Ballot-RadeonSI

[shmerl]

Good to see AMD actually implementing missing functions in Mesa.

[schmidtbag]

Good to see AMD actually implementing missing functions in Mesa.

Agreed. Though I'm not sure how many things will actually use these, as long as the "todo list" is shrinking, I'm happy.

[Veerappan]

I'm not saying it's the ARB shader ballot extension, but doesn't Nouveau already have some form of shader ballot support?

[dungeon]

I guess with AZDO people expect to not be so much CPU bound everywhere, just mine 2c...

They should implement ARB_cpu_boundware_overhaul extension first, otherwise these AZDO techniques will be just ARB_pretty_names

[pal666]

They should implement ARB_cpu_boundware_overhaul extension first, otherwise these AZDO techniques will be just ARB_pretty_names

these azdo techniques are exactly helping with cpu boundness

[zboszor]

Here we are, with the same situation as before. LLVM and Mesa releases are about half way to each other. ARB_shader_ballot requires LLVM 5.0 or later.
See "[PATCH 19/19] radeonsi: enable ARB_shader_ballot"). Mesa 17.1 will be most likely released with this extension in place but LLVM 5.0 is still several months ahead.

Someone (I think Michael Dänzer or some other AMD developer) wrote on this forum that "Mesa cannot support unreleased dependencies", in this case an unreleased LLVM version. But can it require them for enabling features?

What if LLVM 4.0.1 is also fixed for the bug quoted in the last patch for ARB_shader_ballot?
Is there a way to distinguish between LLVM 4.0 and 4.0.1 with an #if conditional so it won't require 5.0?