Mesa's IR Might Get Changed Around Amid Discussions
Phoronix: Mesa's IR Might Get Changed Around Amid Discussions
In a new mailing list thread, Eric Anholt expresses regrets a few years ago when they began sending GLSL IR into their driver rather than using Mesa IR and improving that intermediate representation. Eric is now trying to get the Mesa IR support up to scratch so that it can be sent directly to classic Mesa drivers...
If there is someobody from Intel, please tell us again why you don't want to use TGSI. Back in the days, you were saying that there are no production drivers using it.
Now there are number of production quility drivers using it, apart from propreatary drivers for exotic hardware.
I'm not from Intel, but they have repeatedly said why they are not interested in switching. In short:
Originally Posted by Drago
1. switching requires a huge amount of effort (think man-years)
2. switching would result in worse performance in the short term
3. switching would result in more bugs in the short term
Every hour spent in such a switch would be better-spent improving performance or fixing bugs in the current drivers.
I guess you missed the point of this article, where they say they are interested in switching now.
Originally Posted by BlackStar
The question is what they're going to switch to - something like TGSI, that already exists and is working for other drivers, something like Mesa IR, which already has some code but with tons of issues in the intel driver, or something entirely new that draws experience from all the others. Or just sticking with GLSL IR, i guess.
It they don't like TGSI, they can still help fixing it. There is no poing of number of intermediate languages in Mesa.
Do they have to go full gallium to use TGSI instead of just depending on the galium swrast driver being built and plugging in there somewhere?