diff options
author | Rémi Denis-Courmont <remi@remlab.net> | 2022-09-03 18:05:17 +0300 |
---|---|---|
committer | Martin Storsjö <martin@martin.st> | 2022-09-03 23:54:05 +0300 |
commit | 164021423a25f02c6253bb8d73ae9a443a129381 (patch) | |
tree | ee55146ad3034333f35eb15986086c5e772927b0 /tools/python/convert_from_tensorflow.py | |
parent | 0b95a6a1d0b3d9c06aedd5fc929804661addd263 (diff) | |
download | ffmpeg-164021423a25f02c6253bb8d73ae9a443a129381.tar.gz |
aarch64: relax byte-swap assembler constraints
There are no particular reasons to force the compiler to use the same
register as output and input operand. This forces an extra MOV
instruction if the input value needs to be reused after the swap.
In most cases, this makes no differences, as the compiler will seleect
the same register for both operands either way.
Signed-off-by: Martin Storsjö <martin@martin.st>
Diffstat (limited to 'tools/python/convert_from_tensorflow.py')
0 files changed, 0 insertions, 0 deletions