From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] swscale/x86/yuv2yuvX: Process tails by jumping back into the main loop.
Date: Wed, 6 Sep 2023 18:37:36 +0200
Message-ID: <20230906163736.GO8640@pb2> (raw)
In-Reply-To: <20230906142518.1634649-1-alankelly@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]
On Wed, Sep 06, 2023 at 04:25:00PM +0200, Alan Kelly via ffmpeg-devel wrote:
> ---
> libswscale/x86/swscale.c | 19 ++++++++-----------
> libswscale/x86/yuv2yuvX.asm | 24 ++++++++++++++++++------
> 2 files changed, 26 insertions(+), 17 deletions(-)
ffmpeg -i lena.pnm -vf scale=32:32,scale=4:4 -bitexact -y file4x4.jpg
Duration: N/A, bitrate: N/A
Stream #0:0: Video: ppm, rgb24, 256x256, 25 fps, 25 tbr, 25 tbn
Stream mapping:
Stream #0:0 -> #0:0 (ppm (native) -> mjpeg (native))
Press [q] to stop, [?] for help
[swscaler @ 0x55763d89b740] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x55763d8ab0c0] deprecated pixel format used, make sure you did set range correctly
[swscaler @ 0x55763d89b740] deprecated pixel format used, make sure you did set range correctly
Segmentation fault (core dumped)
tell me if you cannot reproduce then ill generate a proper backtrace
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
than the original author, trying to rewrite it will not make it better.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
prev parent reply other threads:[~2023-09-06 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 14:25 Alan Kelly via ffmpeg-devel
2023-09-06 16:37 ` Michael Niedermayer [this message]
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=20230906163736.GO8640@pb2 \
--to=michael@niedermayer.cc \
--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