+# Introduction
+
+<!-- hide -->
* <https://bugs.libre-soc.org/show_bug.cgi?id=1074>
* <https://libre-soc.org/openpower/sv/biginteger/> for format and
information about implicit RS/FRS
* <https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/decoder/isa/test_caller_svp64_dct.py;hb=HEAD>
* [[openpower/isa/svfparith]]
+* [[openpower/isa/svfixedarith]]
+* [[openpower/sv/rfc/ls016]]
+<!-- show -->
+
+Although best used with SVP64 REMAP these instructions may be used in a Scalar-only
+context to save considerably on DCT, DFT and FFT processing. Whilst some hardware
+implementations may not necessarily implement them efficiently (slower Micro-coding)
+savings still come from the reduction in temporary registers as well as instruction
+count.
-# Twin Butterfly Integer DCT Instruction(s)
+# Rationale for Twin Butterfly Integer DCT Instruction(s)
+
+The number of general-purpose uses for DCT is huge. The number of
+instructions needed instead of these Twin-Butterfly instructions is also
+huge (**eight**) and given that it is extremely common to explicitly
+loop-unroll them quantity hundreds to thousands of instructions are
+dismayingly common (for all ISAs).
The goal is to implement instructions that calculate the expression:
```
-fdct_round_shift((a +/- b) * c)
+ fdct_round_shift((a +/- b) * c)
```
For the single-coefficient butterfly instruction, and:
```
- fdct_round_shift(a * c1 +/- b * c2)
+ fdct_round_shift(a * c1 +/- b * c2)
```
For the double-coefficient butterfly instruction.
-`fdct_round_shift` is defined as `ROUND_POWER_OF_TWO(x, 14)`
+In a 32-bit context `fdct_round_shift` is defined as `ROUND_POWER_OF_TWO(x, 14)`
+
+```
+ #define ROUND_POWER_OF_TWO(value, n) \
+ (((value) + (1 << ((n)-1))) >> (n))
+```
+
+These instructions are at the core of **ALL** FDCT calculations in many
+major video codecs, including -but not limited to- VP8/VP9, AV1, etc.
+ARM includes special instructions to optimize these operations, although
+they are limited in precision: `vqrdmulhq_s16`/`vqrdmulhq_s32`.
+
+The suggestion is to have a single instruction to calculate both values
+`((a + b) * c) >> N`, and `((a - b) * c) >> N`. The instruction will
+run in accumulate mode, so in order to calculate the 2-coeff version
+one would just have to call the same instruction with different order a,
+b and a different constant c.
+
+Example taken from libvpx
+<https://chromium.googlesource.com/webm/libvpx/+/refs/heads/main/vpx_dsp/fwd_txfm.c#132>:
+
+```
+ #include <stdint.h>
+ #define ROUND_POWER_OF_TWO(value, n) \
+ (((value) + (1 << ((n)-1))) >> (n))
+ void twin_int(int16_t *t, int16_t x0, int16_t x1, int16_t cospi_16_64) {
+ t[0] = ROUND_POWER_OF_TWO((x0 + x1) * cospi_16_64, 14);
+ t[1] = ROUND_POWER_OF_TWO((x0 - x1) * cospi_16_64, 14);
+ }
+```
+
+8 instructions are required - replaced by just the one (maddsubrs):
```
-#define ROUND_POWER_OF_TWO(value, n) (((value) + (1 << ((n)-1))) >> (n))
+ add 9,5,4
+ subf 5,5,4
+ mullw 9,9,6
+ mullw 5,5,6
+ addi 9,9,8192
+ addi 5,5,8192
+ srawi 9,9,14
+ srawi 5,5,14
```
-These instructions are at the core of **ALL** FDCT calculations in many major video codecs, including -but not limited to- VP8/VP9, AV1, etc.
-Arm includes special instructions to optimize these operations, although they are limited in precision: `vqrdmulhq_s16`/`vqrdmulhq_s32`.
+-------
-The suggestion is to have a single instruction to calculate both values `((a + b) * c) >> N`, and `((a - b) * c) >> N`.
-The instruction will run in accumulate mode, so in order to calculate the 2-coeff version one would just have to call the same instruction with different order a, b and a different constant c.
+\newpage{}
-## [DRAFT] Integer Butterfly Multiply Add/Sub FFT/DCT
+## Integer Butterfly Multiply Add/Sub FFT/DCT
+
+**Add the following to Book I Section 3.3.9.1**
A-Form
+```
+ |0 |6 |11 |16 |21 |26 |31 |
+ | PO | RT | RA | RB | SH | XO |Rc |
+```
+
* maddsubrs RT,RA,SH,RB
Pseudo-code:
n <- SH
sum <- (RT) + (RA)
diff <- (RT) - (RA)
- prod1 <- MULS(RB, sum)[XLEN:(XLEN*2)-1]
- prod2 <- MULS(RB, diff)[XLEN:(XLEN*2)-1]
- res1 <- ROTL64(prod1, XLEN-n)
- res2 <- ROTL64(prod2, XLEN-n)
- m <- MASK(n, (XLEN-1))
- signbit1 <- res1[0]
- signbit2 <- res2[0]
- smask1 <- ([signbit1]*XLEN) & ¬m
- smask2 <- ([signbit2]*XLEN) & ¬m
- s64_1 <- [0]*(XLEN-1) || signbit1
- s64_2 <- [0]*(XLEN-1) || signbit2
- RT <- (res1 & m | smask1) + s64_1
- RS <- (res2 & m | smask2) + s64_2
+ prod1 <- MULS(RB, sum)
+ prod1_lo <- prod1[XLEN:(XLEN*2)-1]
+ prod2 <- MULS(RB, diff)
+ prod2_lo <- prod2[XLEN:(XLEN*2)-1]
+ if n = 0 then
+ RT <- prod1_lo
+ RS <- prod2_lo
+ else
+ round <- [0]*XLEN
+ round[XLEN -n] <- 1
+ prod1_lo <- prod1_lo + round
+ prod2_lo <- prod2_lo + round
+ m <- MASK(n, (XLEN-1))
+ res1 <- ROTL64(prod1_lo, XLEN-n) & m
+ res2 <- ROTL64(prod2_lo, XLEN-n) & m
+ signbit1 <- prod1_lo[0]
+ signbit2 <- prod2_lo[0]
+ smask1 <- ([signbit1]*XLEN) & ¬m
+ smask2 <- ([signbit2]*XLEN) & ¬m
+ RT <- (res1 | smask1)
+ RS <- (res2 | smask2)
```
-Special Registers Altered:
+Note that if Rc=1 an Illegal Instruction is raised. Rc=1 is `RESERVED`
-```
- None
-```
+Similar to `RTp`, this instruction produces an implicit result, `RS`,
+which under Scalar circumstances is defined as `RT+1`. For SVP64 if
+`RT` is a Vector, `RS` begins immediately after the Vector `RT` where
+the length of `RT` is set by `SVSTATE.MAXVL` (Max Vector Length).
-Where we have added this variant in A-Form (defined in fields.txt):
+Special Registers Altered:
```
-# # 1.6.17 A-FORM
- |0 |6 |11 |16 |21 |26 |31 |
- | PO | RT | RA | RB | SH | XO |Rc |
-
+ None
```
-The instruction has been added to `minor_22.csv`:
+-------
-```
-------01000,ALU,OP_MADDSUBRS,RT,CONST_SH,RB,RT,NONE,CR0,0,0,ZERO,0,NONE,0,0,0,0,1,0,RC_ONLY,0,0,maddsubrs,A,,1,unofficial until submitted and approved/renumbered by the opf isa wg
-```
+\newpage{}
+# Twin Butterfly Floating-Point DCT and FFT Instruction(s)
-# Twin Butterfly Integer DCT Instruction(s)
+**Add the following to Book I Section 4.6.6.3**
-## [DRAFT] Floating Twin Multiply-Add DCT [Single]
+## Floating-Point Twin Multiply-Add DCT [Single]
X-Form
```
|0 |6 |11 |16 |21 |31 |
- | PO | FRT | FRA | FRB | XO | Rc|
+ | PO | FRT | FRA | FRB | XO |Rc |
```
* fdmadds FRT,FRA,FRB (Rc=0)
-* fdmadds. FRT,FRA,FRB (Rc=1)
Pseudo-code:
FRT <- FPMUL32(FRA, sub)
```
+The two IEEE754-FP32 operations
+
+```
+ FRS <- [(FRT) + (FRB)]
+ FRT <- [(FRT) - (FRB)] * (FRA)
+```
+
+are simultaneously performed.
+
+The Floating-Point operand in register FRT is added to the floating-point
+operand in register FRB and the result stored in FRS.
+
+Using the exact same operand input register values from FRT and FRB
+that were used to create FRS, the Floating-Point operand in register
+FRB is subtracted from the floating-point operand in register FRT and
+the result then rounded before being multiplied by FRA to create an
+intermediate result that is stored in FRT.
+
+The add into FRS is treated exactly as `fadds`. The creation of the
+result FRT is **not** the same as that of `fmsubs`, but is instead as if
+`fsubs` were performed first followed by `fmuls`. The creation of FRS
+and FRT are treated as parallel independent operations which occur at
+the same time.
+
+Note that if Rc=1 an Illegal Instruction is raised. Rc=1 is `RESERVED`
+
+Similar to `FRTp`, this instruction produces an implicit result, `FRS`,
+which under Scalar circumstances is defined as `FRT+1`. For SVP64 if
+`FRT` is a Vector, `FRS` begins immediately after the Vector `FRT`
+where the length of `FRT` is set by `SVSTATE.MAXVL` (Max Vector Length).
+
Special Registers Altered:
```
FPRF FR FI
FX OX UX XX
VXSNAN VXISI VXIMZ
- CR1 (if Rc=1)
```
-## [DRAFT] Floating Multiply-Add FFT [Single]
+## Floating-Point Multiply-Add FFT [Single]
X-Form
```
|0 |6 |11 |16 |21 |31 |
- | PO | FRT | FRA | FRB | XO | Rc|
+ | PO | FRT | FRA | FRB | XO |Rc |
```
* ffmadds FRT,FRA,FRB (Rc=0)
-* ffmadds. FRT,FRA,FRB (Rc=1)
Pseudo-code:
FRT <- FPMULADD32(FRT, FRA, FRB, 1, 1)
```
+The two operations
+
+```
+ FRS <- -([(FRT) * (FRA)] - (FRB))
+ FRT <- [(FRT) * (FRA)] + (FRB)
+```
+
+are performed.
+
+The floating-point operand in register FRT is multiplied by the
+floating-point operand in register FRA. The floating-point operand in
+register FRB is added to this intermediate result, and the intermediate
+stored in FRS.
+
+Using the exact same values of FRT, FRT and FRB as used to create
+FRS, the floating-point operand in register FRT is multiplied by the
+floating-point operand in register FRA. The floating-point operand
+in register FRB is subtracted from this intermediate result, and the
+intermediate stored in FRT.
+
+FRT is created as if a `fmadds` operation had been performed. FRS is
+created as if a `fnmsubs` operation had simultaneously been performed
+with the exact same register operands, in parallel, independently,
+at exactly the same time.
+
+FRT is a Read-Modify-Write operation.
+
+Note that if Rc=1 an Illegal Instruction is raised.
+Rc=1 is `RESERVED`
+
+Similar to `FRTp`, this instruction produces an implicit result,
+`FRS`, which under Scalar circumstances is defined as `FRT+1`.
+For SVP64 if `FRT` is a Vector, `FRS` begins immediately after the
+Vector `FRT` where the length of `FRT` is set by `SVSTATE.MAXVL`
+(Max Vector Length).
+
+Special Registers Altered:
+
+```
+ FPRF FR FI
+ FX OX UX XX
+ VXSNAN VXISI VXIMZ
+```
+
+## Floating-Point Twin Multiply-Add DCT
+
+X-Form
+
+```
+ |0 |6 |11 |16 |21 |31 |
+ | PO | FRT | FRA | FRB | XO |Rc |
+```
+
+* fdmadd FRT,FRA,FRB (Rc=0)
+
+Pseudo-code:
+
+```
+ FRS <- FPADD64(FRT, FRB)
+ sub <- FPSUB64(FRT, FRB)
+ FRT <- FPMUL64(FRA, sub)
+```
+
+The two IEEE754-FP64 operations
+
+```
+ FRS <- [(FRT) + (FRB)]
+ FRT <- [(FRT) - (FRB)] * (FRA)
+```
+
+are simultaneously performed.
+
+The Floating-Point operand in register FRT is added to the floating-point
+operand in register FRB and the result stored in FRS.
+
+Using the exact same operand input register values from FRT and FRB
+that were used to create FRS, the Floating-Point operand in register
+FRB is subtracted from the floating-point operand in register FRT and
+the result then rounded before being multiplied by FRA to create an
+intermediate result that is stored in FRT.
+
+The add into FRS is treated exactly as `fadd`. The creation of the
+result FRT is **not** the same as that of `fmsub`, but is instead as if
+`fsub` were performed first followed by `fmuls. The creation of FRS
+and FRT are treated as parallel independent operations which occur at
+the same time.
+
+Note that if Rc=1 an Illegal Instruction is raised. Rc=1 is `RESERVED`
+
+Similar to `FRTp`, this instruction produces an implicit result, `FRS`,
+which under Scalar circumstances is defined as `FRT+1`. For SVP64 if
+`FRT` is a Vector, `FRS` begins immediately after the Vector `FRT`
+where the length of `FRT` is set by `SVSTATE.MAXVL` (Max Vector Length).
+
Special Registers Altered:
```
FPRF FR FI
FX OX UX XX
VXSNAN VXISI VXIMZ
- CR1 (if Rc=1)
+```
+
+## Floating-Point Twin Multiply-Add FFT
+
+X-Form
+
+```
+ |0 |6 |11 |16 |21 |31 |
+ | PO | FRT | FRA | FRB | XO |Rc |
+```
+
+* ffmadd FRT,FRA,FRB (Rc=0)
+
+Pseudo-code:
+
+```
+ FRS <- FPMULADD64(FRT, FRA, FRB, -1, 1)
+ FRT <- FPMULADD64(FRT, FRA, FRB, 1, 1)
+```
+
+The two operations
+
+```
+ FRS <- -([(FRT) * (FRA)] - (FRB))
+ FRT <- [(FRT) * (FRA)] + (FRB)
+```
+
+are performed.
+
+The floating-point operand in register FRT is multiplied by the
+floating-point operand in register FRA. The float- ing-point operand in
+register FRB is added to this intermediate result, and the intermediate
+stored in FRS.
+
+Using the exact same values of FRT, FRT and FRB as used to create
+FRS, the floating-point operand in register FRT is multiplied by the
+floating-point operand in register FRA. The float- ing-point operand
+in register FRB is subtracted from this intermediate result, and the
+intermediate stored in FRT.
+
+FRT is created as if a `fmadd` operation had been performed. FRS is
+created as if a `fnmsub` operation had simultaneously been performed
+with the exact same register operands, in parallel, independently,
+at exactly the same time.
+
+FRT is a Read-Modify-Write operation.
+
+Note that if Rc=1 an Illegal Instruction is raised. Rc=1 is `RESERVED`
+
+Similar to `FRTp`, this instruction produces an implicit result, `FRS`,
+which under Scalar circumstances is defined as `FRT+1`. For SVP64 if
+`FRT` is a Vector, `FRS` begins immediately after the Vector `FRT`
+where the length of `FRT` is set by `SVSTATE.MAXVL` (Max Vector Length).
+
+Special Registers Altered:
+
+```
+ FPRF FR FI
+ FX OX UX XX
+ VXSNAN VXISI VXIMZ
+```
+
+
+## Floating-Point Add FFT/DCT [Single]
+
+A-Form
+
+```
+ |0 |6 |11 |16 |21 |26 |31 |
+ | PO | FRT | FRA | FRB | / | XO |Rc |
+```
+
+* ffadds FRT,FRA,FRB (Rc=0)
+
+Pseudo-code:
+
+```
+ FRT <- FPADD32(FRA, FRB)
+ FRS <- FPSUB32(FRB, FRA)
+```
+
+Special Registers Altered:
+
+```
+ FPRF FR FI
+ FX OX UX XX
+ VXSNAN VXISI
+```
+
+## Floating-Point Add FFT/DCT [Double]
+
+A-Form
+
+```
+ |0 |6 |11 |16 |21 |26 |31 |
+ | PO | FRT | FRA | FRB | / | XO |Rc |
+```
+
+* ffadd FRT,FRA,FRB (Rc=0)
+
+Pseudo-code:
+
+```
+ FRT <- FPADD64(FRA, FRB)
+ FRS <- FPSUB64(FRB, FRA)
+```
+
+Special Registers Altered:
+
+```
+ FPRF FR FI
+ FX OX UX XX
+ VXSNAN VXISI
+```
+
+## Floating-Point Subtract FFT/DCT [Single]
+
+A-Form
+
+```
+ |0 |6 |11 |16 |21 |26 |31 |
+ | PO | FRT | FRA | FRB | / | XO |Rc |
+```
+
+* ffsubs FRT,FRA,FRB (Rc=0)
+
+Pseudo-code:
+
+```
+ FRT <- FPSUB32(FRB, FRA)
+ FRS <- FPADD32(FRA, FRB)
+```
+
+Special Registers Altered:
+
+```
+ FPRF FR FI
+ FX OX UX XX
+ VXSNAN VXISI
+```
+
+## Floating-Point Subtract FFT/DCT [Double]
+
+A-Form
+
+```
+ |0 |6 |11 |16 |21 |26 |31 |
+ | PO | FRT | FRA | FRB | / | XO |Rc |
+```
+
+* ffsub FRT,FRA,FRB (Rc=0)
+
+Pseudo-code:
+
+```
+ FRT <- FPSUB64(FRB, FRA)
+ FRS <- FPADD64(FRA, FRB)
+```
+
+Special Registers Altered:
+
+```
+ FPRF FR FI
+ FX OX UX XX
+ VXSNAN VXISI
```