From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avutil/x86/intmath: remove inline asm implementations for clip functions
Date: Wed, 04 Jun 2025 14:33:02 +0300
Message-ID: <EEE2353E-8D25-44EA-869C-CB8B81E93056@remlab.net> (raw)
In-Reply-To: <20250603181557.GB181379@haasn.xyz>
Le 3 juin 2025 19:15:57 GMT+03:00, Niklas Haas <ffmpeg@haasn.xyz> a écrit :
>On Mon, 02 Jun 2025 15:41:33 -0300 James Almer <jamrial@gmail.com> wrote:
>> GCC/Clang is smart enough to emit minss/maxss the same way as these functions.
>> The only theoretical benefit was in x86_32, where x87 floats are used, but the
>> penalty of making the clipping opaque to the compiler's scheduler plus moving
>> values from mmx regs to xmm and back will offset any potential speedup.
>> x86_32 builds targetting anything made in the last two decades and a half
>> should use -msse -mfp=sse anyway.
>
>As mention in the another thread, x87 FPU usage causes non-bitexact results in
>swscale. Should we at this point consider setting -mfpu=sse by default for
>x86_32 builds?
As a general rule, I prefer to leave the choice of compiler flags to the distributor than to hard-code them in project specific build scripts.
_______________________________________________
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".
prev parent reply other threads:[~2025-06-04 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 18:41 James Almer
2025-06-03 16:15 ` Niklas Haas
2025-06-03 16:22 ` Andreas Rheinhardt
2025-06-03 16:32 ` Niklas Haas
2025-06-03 16:40 ` Martin Storsjö
2025-06-04 11:33 ` Rémi Denis-Courmont [this message]
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=EEE2353E-8D25-44EA-869C-CB8B81E93056@remlab.net \
--to=remi@remlab.net \
--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