From: Niklas Haas <ffmpeg@haasn.xyz> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avutil/x86/intmath: remove inline asm implementations for clip functions Date: Tue, 3 Jun 2025 18:32:32 +0200 Message-ID: <20250603183232.GB184053@haasn.xyz> (raw) In-Reply-To: <GV1P250MB0737BF0E46A2DCA9FFDD8F968F6DA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> On Tue, 03 Jun 2025 18:22:30 +0200 Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote: > Niklas Haas: > > 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? > > > What about CPUs without SSE? Have been dropped from all major distros, as far as I can tell, so I'm not sure what userbase we would be alienating by not supporting them out of the box. If you have a valid use case for combining FFmpeg git master builds from 2025 with obsolete hardware 1999, you can just disable the flag and live with the fact that your output will not be bitexact. > > - Andreas > > _______________________________________________ > 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". _______________________________________________ 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:[~2025-06-03 16:32 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 [this message] 2025-06-03 16:40 ` Martin Storsjö 2025-06-04 11:33 ` Rémi Denis-Courmont
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=20250603183232.GB184053@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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