From d317944c245a0400a94380ba064d53aec9c5a452 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Alejandro=20Pi=C3=B1eiro?= Date: Thu, 13 Jun 2019 13:22:40 +0200 Subject: [PATCH] docs: document three NIR_ envvars Initially I was only interested on documenting NIR_PRINT, as today I needed to check the code to find this envvar, that at the moment I vaguely remembered that existed. As we are here, though, let's just document all of them (assuming that makes sense). Reviewed-by: Eric Anholt --- docs/envvars.html | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/envvars.html b/docs/envvars.html index 5c4ca905e95..92f9207c80e 100644 --- a/docs/envvars.html +++ b/docs/envvars.html @@ -210,6 +210,23 @@ sometimes be useful for debugging end-user issues. +

NIR passes enviroment variables

+

+The following are only applicable for drivers that uses NIR, as they +modify the behaviour for the common NIR_PASS and NIR_PASS_V macros, +that wrap calls to NIR lowering/optimizations. +

+ +
+
NIR_PRINT
+
If defined, the resulting NIR shader will be printed out at each succesful NIR lowering/optimization call.
+
NIR_TEST_CLONE
+
If defined, cloning a NIR shader would be tested at each succesful NIR lowering/optimization call.
+
NIR_TEST_SERIALIZE
+
If defined, serialize and deserialize a NIR shader would be tested at each succesful NIR lowering/optimization call.
+
+ +

Mesa Xlib driver environment variables

-- 2.30.2