From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] swscale/x86/rgb2rgb: add SSE2 shuffle_bytes functions
Date: Sun, 09 Jun 2024 19:05:34 +0300
Message-ID: <10477469.nUPlyArG6x@basile.remlab.net> (raw)
In-Reply-To: <0bd4d84b-83a0-4b94-95f2-63bcd971a7c6@gmail.com>
Le sunnuntaina 9. kesäkuuta 2024, 18.36.35 EEST James Almer a écrit :
> I obviously don't have that kind of information. You'd need to look at
> things like Steam's, Firefox's or Chrome's hardware surveys.
As discussed on IRC yesterday, Steam claims that 106.85% of processors support
SSE2 (and as many SSE3) but "only" 106.63% support SSSE3 (seriously). What
100% are, I don't know. AVX2 is close with 99.83% but no cigar.
In any case, there is a tiny but observable gap between SSE2 and SSSE3 there.
> >> It was easy to write and i don't feel particularly interested enough to
> >> argue, so if you think it's not worth adding, i can just remove the
> >> mmxext version and skip adding anything.
> >
> > I think we should not optimize for CPUs that do not even have x86-64 v2.
>
> What is x86-64 v2?
See
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level
--
雷米‧德尼-库尔蒙
http://www.remlab.net/
_______________________________________________
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-06-09 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 20:51 [FFmpeg-devel] [PATCH] swscale/x86/rgb2rgb: replace shuffle_bytes_2103_mmxext with an SSE2 version James Almer
2024-06-06 14:15 ` [FFmpeg-devel] [PATCH] swscale/x86/rgb2rgb: add SSE2 shuffle_bytes functions James Almer
2024-06-06 14:48 ` Andreas Rheinhardt
2024-06-06 15:45 ` James Almer
2024-06-08 15:55 ` Andreas Rheinhardt
2024-06-08 16:21 ` Rémi Denis-Courmont
2024-06-09 15:36 ` James Almer
2024-06-09 16:05 ` Rémi Denis-Courmont [this message]
2024-06-10 17:06 ` James Almer
2024-06-11 5:18 ` Andreas Rheinhardt
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=10477469.nUPlyArG6x@basile.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