summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTriang3l <triang3l@yandex.ru>2020-12-10 12:39:02 +0300
committerTriang3l <triang3l@yandex.ru>2020-12-10 12:39:02 +0300
commit8bcfcf64525a956e29ffcd00febc134e49e2678f (patch)
tree3a54d28afcbb0f8a075f647fa3b177fe64104059
parentbc0c2040e275d5684ca66dbf17d63e4b172052b7 (diff)
[GPU] Update v_mad_legacy_f32 comment
-rw-r--r--src/xenia/gpu/ucode.h9
1 files changed, 5 insertions, 4 deletions
diff --git a/src/xenia/gpu/ucode.h b/src/xenia/gpu/ucode.h
index 85b52a377..ea11f10cd 100644
--- a/src/xenia/gpu/ucode.h
+++ b/src/xenia/gpu/ucode.h
@@ -816,10 +816,11 @@ static_assert_size(TextureFetchInstruction, 12);
// move of the third operand in case of zero multiplicands, because the term
// may be -0, while the result should be +0 in this case.
// http://developer.amd.com/wordpress/media/2013/10/R5xx_Acceleration_v1.5.pdf
-// Multiply-add also appears to be not fused (the SM3 behavior instruction on
-// GCN is called v_mad_legacy_f32, not v_fma_legacy_f32) - shader translators
-// should not use instructions that may be interpreted by the host GPU as
-// fused multiply-add.
+// Multiply-add also appears to be not fused; the SM3 behavior instruction on
+// GCN is called v_mad_legacy_f32, not v_fma_legacy_f32 (in 2012-2020, before
+// RDNA 2, which removed v_mad_f32 as well) - shader translators should not
+// use instructions that may be interpreted by the host GPU as fused
+// multiply-add.
enum class AluScalarOpcode : uint32_t {
// Floating-Point Add