From 8e099755624b8854acd83e4f2704ee57409307bb Mon Sep 17 00:00:00 2001 From: Erik Faye-Lund Date: Wed, 19 Oct 2022 12:48:46 +0200 Subject: [PATCH] docs: adreno -> Adreno Reviewed-by: David Heidelberg Part-of: --- docs/drivers/freedreno/ir3-notes.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/drivers/freedreno/ir3-notes.rst b/docs/drivers/freedreno/ir3-notes.rst index 0d859813d5f..093d7c5bd2a 100644 --- a/docs/drivers/freedreno/ir3-notes.rst +++ b/docs/drivers/freedreno/ir3-notes.rst @@ -1,7 +1,7 @@ IR3 NOTES ========= -Some notes about ir3, the compiler and machine-specific IR for the shader ISA introduced with adreno a3xx. The same shader ISA is present, with some small differences, in adreno a4xx. +Some notes about ir3, the compiler and machine-specific IR for the shader ISA introduced with Adreno a3xx. The same shader ISA is present, with some small differences, in Adreno a4xx. Compared to the previous generation a2xx ISA (ir2), the a3xx ISA is a "simple" scalar instruction set. However, the compiler is responsible, in most cases, to schedule the instructions. The hardware does not try to hide the shader core pipeline stages. For a common example, a common (cat2) ALU instruction takes four cycles, so a subsequent cat2 instruction which uses the result must have three intervening instructions (or NOPs). When operating on vec4's, typically the corresponding scalar instructions for operating on the remaining three components could typically fit. Although that results in a lot of edge cases where things fall over, like: