From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] New swscale internal design prototype
Date: Sun, 9 Mar 2025 18:11:54 +0200 (EET)
Message-ID: <518838a-a82c-c585-c1f6-80d17197edc5@martin.st> (raw)
In-Reply-To: <20250308235342.GB669161@haasn.xyz>
On Sat, 8 Mar 2025, Niklas Haas wrote:
> What are the thoughts on the float-first approach?
In general, for modern architectures, relying on floats probably is
reasonable. (On architectures that aren't of quite as widespread interest,
it might not be so clear cut though.)
However with the benchmark example you provided a couple of weeks ago, we
concluded that even on x86 on modern HW, floats were faster than int16
only in one case: When using Clang, not GCC, and when compiling with
-mavx2, not without it. In all the other cases, int16 was faster than
float.
After doing those benchmarks, my understanding was that you concluded that
we probably need to keep int16 based codepaths still, then.
Did something fundamental come up since we did these benchmarks that
changed your conclusion?
// 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:[~2025-03-09 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 22:53 Niklas Haas
2025-03-09 16:11 ` Martin Storsjö [this message]
2025-03-09 19:45 ` Niklas Haas
2025-03-09 18:18 ` Rémi Denis-Courmont
2025-03-09 19:57 ` Niklas Haas
2025-03-10 0:57 ` Rémi Denis-Courmont
2025-03-09 19:41 ` Michael Niedermayer
2025-03-09 21:13 ` Niklas Haas
2025-03-09 21:28 ` Niklas Haas
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=518838a-a82c-c585-c1f6-80d17197edc5@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