From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] get_cabac_inline_x86: Don't inline if 32-bit Windows
Date: Tue, 3 Jan 2023 00:35:43 +0100
Message-ID: <CA+anqdwvkxRCg4xtUw8WaXvuwkXtK6JTbDTare6=jjH=ihxBJQ@mail.gmail.com> (raw)
In-Reply-To: <20230102230128.972907-1-ccom@randomderp.com>
On Tue, Jan 3, 2023 at 12:01 AM Christopher Degawa <ccom@randomderp.com> wrote:
>
> previouslly, it only was an issue with 32-bit clang from msys2's
> mingw32 repo, however, at some point with an update to gcc 12.2.0,
> the same issue popped up. Tested with a clean clone of ffmpeg, and even
> tested with n5.0, but the issue persists, so I presume it's a compiler
> issue.
>
> Related: https://trac.ffmpeg.org/ticket/8903
>
I regularly build with 12.2 on win32 and its fine.
In fact, there is a fate station for that:
https://fate.ffmpeg.org/report.cgi?slot=x86_32-mingw-w64-dll-windows-native&time=20230102232810
So if you are seeing this issue, more details that trigger it will be
required, and maybe a more targeted fix.
- Hendrik
_______________________________________________
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-01-02 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 23:01 Christopher Degawa
2023-01-02 23:35 ` Hendrik Leppkes [this message]
2023-01-03 18:32 ` Christopher Degawa
2023-01-03 18:45 ` Christopher Degawa
2023-01-03 10:15 ` Andreas Rheinhardt
2023-01-03 18:51 ` Christopher Degawa
2023-01-03 19:18 ` Christopher Degawa
2023-03-27 11:34 ` Martin Storsjö
2023-03-27 17:59 ` Christopher Degawa
2023-03-27 20:08 ` Martin Storsjö
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='CA+anqdwvkxRCg4xtUw8WaXvuwkXtK6JTbDTare6=jjH=ihxBJQ@mail.gmail.com' \
--to=h.leppkes@gmail.com \
--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