From 0f6be273f1e3fb880c572e4283623d8e4ecbe0b1 Mon Sep 17 00:00:00 2001 From: Daniel Stone Date: Thu, 12 Sep 2024 15:32:07 +0100 Subject: [PATCH] doc/vc4: Remove reference to old shader-db Piglit has the traces now. Signed-off-by: Daniel Stone Part-of: --- docs/drivers/vc4.rst | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/docs/drivers/vc4.rst b/docs/drivers/vc4.rst index 50eb7011590..f543fa50bcd 100644 --- a/docs/drivers/vc4.rst +++ b/docs/drivers/vc4.rst @@ -267,24 +267,17 @@ the counters, you can work out which ones they were at the GL level by opening the trace up in qapitrace and using ``^-G`` to jump to that call number and ``^-L`` to look up the GL state at that call. -shader-db ---------- +Trace Testing +------------- shader-db is often used as a proxy for real-world app performance when working on the compiler in Mesa. On VC4, there is a lot of state-dependent code in the shaders (like blending or vertex attribute format handling), so the typical `shader-db `__ will miss important -areas for optimization. Instead, anholt wrote a `new one -`__ based on -apitraces. Once you have a collection of traces, starting from -`traces-db `__, -you can test a compiler change in this shader-db with:: - - ./run.py > before - (cd ../mesa && make install) - ./run.py > after - ./report.py before after +areas for optimization. Piglit can instead test apitraces, such as +those captured in +`traces-db `__. Hardware Documentation ----------------------