docs/relnotes: add support for VK_KHR_shader_float16_int8

[mesa.git] / docs / viewperf.html

diff --git a/docs/viewperf.html b/docs/viewperf.html
index 6b63b94d8526b010eb08dbc380db1182b3227613..ed89ee2cfeaf7cb63399c1db0318940c909187ec 100644 (file)
--- a/docs/viewperf.html
+++ b/docs/viewperf.html
@@ -18,8 +18,8 @@
 
 <p>
 This page lists known issues with
-<a href="http://www.spec.org/gwpg/gpc.static/vp11info.html" target="_main">SPEC Viewperf 11</a>
-and <a href="https://www.spec.org/gwpg/gpc.static/vp12info.html" target="_main">SPEC Viewperf 12</a>
+<a href="https://www.spec.org/gwpg/gpc.static/vp11info.html">SPEC Viewperf 11</a>
+and <a href="https://www.spec.org/gwpg/gpc.static/vp12info.html">SPEC Viewperf 12</a>
 when running on Mesa-based drivers.
 </p>
 
@@ -66,13 +66,10 @@ either in Viewperf or the Mesa driver.
 
 <p>
 These tests use features of the
-<a href="http://www.opengl.org/registry/specs/NV/fragment_program2.txt"
-target="_main">
-GL_NV_fragment_program2</a> and
-<a href="http://www.opengl.org/registry/specs/NV/vertex_program3.txt"
-target="_main">
-GL_NV_vertex_program3</a> extensions without checking if the driver supports
-them.
+<a href="https://www.opengl.org/registry/specs/NV/fragment_program2.txt">GL_NV_fragment_program2</a>
+and
+<a href="https://www.opengl.org/registry/specs/NV/vertex_program3.txt">GL_NV_vertex_program3</a>
+extensions without checking if the driver supports them.
 </p>
 <p>
 When Mesa tries to compile the vertex/fragment programs it generates errors
@@ -86,8 +83,8 @@ Subsequent drawing calls become no-ops and the rendering is incorrect.
 
 <p>
 These tests depend on the
-<a href="http://www.opengl.org/registry/specs/NV/primitive_restart.txt"
-target="_main">GL_NV_primitive_restart</a> extension.
+<a href="https://www.opengl.org/registry/specs/NV/primitive_restart.txt">GL_NV_primitive_restart</a>
+extension.
 </p>
 
 <p>
@@ -124,7 +121,7 @@ never specified.
 
 <p>
 A trace captured with
-<a href="https://github.com/apitrace/apitrace" target="_main">API trace</a>
+<a href="https://github.com/apitrace/apitrace">API trace</a>
 shows this sequences of calls like this:
 
 <pre>
@@ -329,6 +326,13 @@ array initializer statement, but it neglects to specify
 <code>#version 120</code> at the top of the shader code.
 So, the shader does not compile and all that's rendered is plain white polygons.
 </p>
+<p>
+Also, the test tries to create a very large 3D texture that may exceed
+the device driver's limit.
+When this happens, the glTexImage3D call fails and all that's rendered is
+a white box.
+</p>
+
 
 <h3>showcase-01</h3>