From: Jacob Lifshay <programmerjake@gmail.com>
Date: Sat, 15 Apr 2023 01:47:16 +0000 (-0700)
Subject: add lkcl's justification for fmin/fmax
X-Git-Tag: opf_rfc_ls008_v1~2
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=70dda033b8caf1bcfcd53302b6e04481a5b8b787;p=libreriscv.git

add lkcl's justification for fmin/fmax
---

diff --git a/openpower/sv/rfc/ls013.mdwn b/openpower/sv/rfc/ls013.mdwn
index 4b8ac5f8b..6341e572e 100644
--- a/openpower/sv/rfc/ls013.mdwn
+++ b/openpower/sv/rfc/ls013.mdwn
@@ -65,7 +65,9 @@ TODO
     SVP64 tree reduction needs a single instruction to work properly.
 2. if you implement any of the FP min/max modes, the rest are not much more
     hardware.
-3. FP min/max are rather complex to implement in software, the most commonly
+3. TODO(lkcl): fill out: that using VSX may have different meaning (SVP64/VSX)
+    so it is *really* crucial to have SVP64/SFFS ops.
+4. FP min/max are rather complex to implement in software, the most commonly
     used FP max function `fmax` from glibc compiled for SFFS is 32 (!)
     instructions.