From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 4D7A34DA81 for ; Tue, 3 Jun 2025 16:32:44 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 40A1368CAF5; Tue, 3 Jun 2025 19:32:40 +0300 (EEST) Received: from haasn.dev (haasn.dev [78.46.187.166]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 0695668D46C for ; Tue, 3 Jun 2025 19:32:32 +0300 (EEST) Received: from haasn.dev (unknown [10.30.1.1]) by haasn.dev (Postfix) with UTF8SMTP id C83414418B for ; Tue, 3 Jun 2025 18:32:32 +0200 (CEST) Date: Tue, 3 Jun 2025 18:32:32 +0200 Message-ID: <20250603183232.GB184053@haasn.xyz> From: Niklas Haas To: ffmpeg-devel@ffmpeg.org In-Reply-To: References: <20250602184133.2175-1-jamrial@gmail.com> <20250603181557.GB181379@haasn.xyz> MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [FFmpeg-devel] [PATCH] avutil/x86/intmath: remove inline asm implementations for clip functions X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On Tue, 03 Jun 2025 18:22:30 +0200 Andreas Rheinhardt wrote: > Niklas Haas: > > On Mon, 02 Jun 2025 15:41:33 -0300 James Almer 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".