From: Henrik Gramner via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Henrik Gramner <henrik@gramner.com>
Subject: Re: [FFmpeg-devel] [PATCH 1/4] avutil/x86/pixelutils: Empty MMX state in ff_pixelutils_sad_8x8_mmxext
Date: Wed, 1 Nov 2023 12:02:00 +0100
Message-ID: <CAFGUN0rqqEQgOavFKFOp3eUFn_erZUMw9Wu+jvHBjvXU6YRKaQ@mail.gmail.com> (raw)
In-Reply-To: <GV1SPRMB0033280C6F96AACB191058008FA7A@GV1SPRMB0033.EURP250.PROD.OUTLOOK.COM>
On Wed, Nov 1, 2023 at 10:44 AM Andreas Rheinhardt
<andreas.rheinhardt@outlook.com> wrote:
> libavutil/x86/pixelutils.asm | 1 +
> 1 file changed, 1 insertion(+)
IIRC the emms instructions is quite slow on many systems, so if this
is the only pixelutils function using mmx it's probably better to just
rewrite it to use SSE2 instead (even if that means only using the
lower half of xmm registers).
_______________________________________________
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:[~2023-11-01 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 9:45 Andreas Rheinhardt
2023-11-01 9:48 ` [FFmpeg-devel] [PATCH 2/4] avfilter/vf_mpdecimate: Remove emms_c Andreas Rheinhardt
2023-11-01 9:48 ` [FFmpeg-devel] [PATCH 3/4] avfilter/vf_deshake: Remove unnecessary emms_c Andreas Rheinhardt
2023-11-01 9:48 ` [FFmpeg-devel] [PATCH 4/4] avfilter/deshake: Merge header into its only user Andreas Rheinhardt
2023-11-01 11:02 ` Henrik Gramner via ffmpeg-devel [this message]
2023-11-01 11:23 ` [FFmpeg-devel] [PATCH 1/4] avutil/x86/pixelutils: Empty MMX state in ff_pixelutils_sad_8x8_mmxext Andreas Rheinhardt
2023-11-03 11:15 ` 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=CAFGUN0rqqEQgOavFKFOp3eUFn_erZUMw9Wu+jvHBjvXU6YRKaQ@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=henrik@gramner.com \
/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