Running The RadeonSI NIR Back-End With Mesa 19.1 Git

[nuetzel]

Does anyone experience longer shader compile times with NIR? I'm not entirely sure if that's the right description for the problem.

With RuneScape's NXT (C++) client, if I use NIR, new shaders that need cached pause the rendering noticeably longer (like 3-7 second pauses initially without a cache when teleporting to a new area) than without NIR. But it seems once the shaders are cached, there's no problem. It does this on LLVM 7.0 and Mesa 18.1.3 (or something in the 18 series on Fedora 29), and a git build of Mesa 19 and LLVM 9.0 (che-mesa and che-llvm on F29)

Yes, it's there, but worked on (Timo). (Have a look into mesa-devel: 'nir - compiler optimization' / slow compile times...)

Does anyone experience longer shader compile times with NIR? I'm not entirely sure if that's the right description for the problem.

With RuneScape's NXT (C++) client, if I use NIR, new shaders that need cached pause the rendering noticeably longer (like 3-7 second pauses initially without a cache when teleporting to a new area) than without NIR. But it seems once the shaders are cached, there's no problem. It does this on LLVM 7.0 and Mesa 18.1.3 (or something in the 18 series on Fedora 29), and a git build of Mesa 19 and LLVM 9.0 (che-mesa and che-llvm on F29)

[nuetzel]

Can confirm. Those sdma patches immediately freeze the whole system. Even if it's just the desktop.

It is FIXED with Marek's v2 version (Patchwork Mesa).

https://lists.freedesktop.org/archives/mesa-dev/2019-February/215579.html

[Strunkenbold]

Can confirm. Those sdma patches immediately freeze the whole system. Even if it's just the desktop.

[nuetzel]

Note:
It was tested with Vega, here.
I see one little triangle corruption under UH with Polaris 20 (RX580). - Marek know that.
The above corruption is FIXED with current Mesa git.

Yes, this is SOLVED with NIR, even on Polaris. - GREAT.
(Have to bisect for the right commit.)

Marek's latest SDMA patches.
BUT sadly reliable _whole_ system hang under UH and UV with my Polaris 20 (Nitro+) => VM faults (I've to dig.)

Reverting the SDMA patches (1-4) on Polaris SOLVED this.

[clapbr]

You should also log CPU usage during the run...

this. you don't even know if that testcase is CPU-bottlenecked for you and assumed wrong stuff as usual

[cb88]

I tested NIR with the Superposition 1080p extreme benchmark and RX570:

Original R600_DEBUG=nir
1867 1878 points
13.97 14.05 avg fps

No reason to use R600_DEBUG=nir.

You should also log CPU usage during the run...

[Dukenukemx]

And yet no one cares in the Windows world as games use DirectX and not OpenGL.

Emulators tend to use OpenGL like CEMU, YUZU, and Citra. Which all run like crap on AMD in Windows due to poor OpenGL drivers. Run these emulators on Linux and the performance is far better.

[cb88]

Well No Mans Sky somehow runs decent under windows and OpenGL, so I dunno.

Probably because it also Targets PS4 and Xbox both of which have Radeon GPUs so they target the compatible subset of OpenGL instead of trying to optimise for Nvidia etc... its just optimized more generally.

[geearf]

Congratulations to the devs, it's not finished and yet already faster!
It'd be awesome if the min could also be higher than with TGSI of course.

Is the support of OGL 4.5 complete with NIR already?