aboutsummaryrefslogtreecommitdiffstats
path: root/tests/checkasm/Makefile
diff options
context:
space:
mode:
authorRĂ©mi Denis-Courmont <remi@remlab.net>2022-10-06 21:46:12 +0300
committerLynne <dev@lynne.ee>2022-10-10 02:23:18 +0200
commit105921251ab35b870887e0c7348016f4dff3ec5b (patch)
tree08d2d68c6304aca51aa3b931b5ea0282334de2d5 /tests/checkasm/Makefile
parentbfc69297c5d8d130b9cf1082dd1728b39a0e75f6 (diff)
downloadffmpeg-105921251ab35b870887e0c7348016f4dff3ec5b.tar.gz
lavc/aacpsdsp: fix clobber on RISC-V LP64D/ILP32D
Although the DSP function only uses single precision from RISC-V F, the caller may leave double precision values in the spilled registers if the calling convention supports double precision hardware floats. Then, we need to save and restore FS registers as double precision. Conversely, we do not need to save anything at all if an integer calling convention is in use. However we can assume that single precision floats are supported, since the Zve32f extension implies the F extension. So for the sake of simplicity, we always save at least single precision values. In theory, we should even save quadruple precision values if the LP64Q ABI is in use. I have yet to see a compiler that supports it though.
Diffstat (limited to 'tests/checkasm/Makefile')
0 files changed, 0 insertions, 0 deletions