From: "Martin Storsjö" <martin@martin.st>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] x86: Remove inline MMX assembly that clobbers the FPU state
Date: Fri, 26 Jan 2024 15:45:12 +0200 (EET)
Message-ID: <ae537f77-ea2b-7340-e8-dcbe6c9d6473@martin.st> (raw)
In-Reply-To: <20240126130427.2159537-1-martin@martin.st>
On Fri, 26 Jan 2024, Martin Storsjö wrote:
> These inline implementations of AV_COPY64, AV_SWAP64 and AV_ZERO64
> are known to clobber the FPU state - which has to be restored
> with the 'emms' instruction afterwards.
>
> This was known and signaled with the FF_COPY_SWAP_ZERO_USES_MMX
> define, which calling code seems to have been supposed to check,
> in order to call emms_c() after using them. See
> 0b1972d4096df5879038f0af776f87f41e90ebd4,
> 29c4c0886d143790fcbeddbe40a23dfc6f56345c and
> df215e575850e41b19aeb1fd99e53372a6b3d537 for history on earlier
> fixes in the same area.
>
> However, new code can use these AV_*64() macros without knowing
> about the need to call emms_c().
>
> Just get rid of these dangerous inline assembly snippets; this
> doesn't make any difference for 64 bit architectures anyway.
>
> Signed-off-by: Martin Storsjö <martin@martin.st>
> ---
> libavcodec/dca_core.c | 16 ----------------
> libavutil/x86/intreadwrite.h | 36 ------------------------------------
> 2 files changed, 52 deletions(-)
I forgot to add some more context here; the VVC tests fail on i386 in some
cases.
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20240125170518.61211-1-post@frankplowman.com/
fixes this, by using av_log2() instead of the float log2() in the VVC
decoder. This patch fixes the same issue as well, by eliminating the FPU
state clobbering (so that float math functions anywhere in decoders work
as expected).
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-01-26 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 13:04 Martin Storsjö
2024-01-26 13:45 ` Martin Storsjö [this message]
2024-01-27 5:44 ` Nuo Mi
2024-02-09 11:06 ` Martin Storsjö
2024-02-09 15:23 ` Anton Khirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae537f77-ea2b-7340-e8-dcbe6c9d6473@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git