On Tue, Jan 3, 2023 at 12:51 PM Christopher Degawa
wrote:
>
>
> On Tue, Jan 3, 2023 at 4:16 AM Andreas Rheinhardt <
> andreas.rheinha...@outlook.com> wrote:
>
>> Christopher Degawa:
>> > previouslly, it only was an issue with 32-bit clang from msys2's
>> > mingw32 repo, however, at some point wit
On Tue, Jan 3, 2023 at 4:16 AM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Christopher Degawa:
> > 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 c
On Tue, Jan 3, 2023 at 12:32 PM Christopher Degawa
wrote:
>
>
> On Mon, Jan 2, 2023 at 5:36 PM Hendrik Leppkes
> wrote:
>
>> On Tue, Jan 3, 2023 at 12:01 AM Christopher Degawa
>> wrote:
>> >
>>
>> I regularly build with 12.2 on win32 and its fine.
>>
>> In fact, there is a fate station for that
On Mon, Jan 2, 2023 at 5:36 PM Hendrik Leppkes wrote:
> On Tue, Jan 3, 2023 at 12:01 AM Christopher Degawa
> wrote:
> >
>
> 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-n
Christopher Degawa:
> 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 compi
On Tue, Jan 3, 2023 at 12:01 AM Christopher Degawa 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
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:/