From: "Martin Storsjö" <martin@martin.st>
To: Jiawei <jiawei@iscas.ac.cn>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v5] gcc: Don't disable '-ftree-vectorize' if gcc version higher than 13.
Date: Thu, 10 Jul 2025 15:44:56 +0300 (EEST)
Message-ID: <fc22bc72-c4d7-7b53-ae50-1ff5fd02fbb@martin.st> (raw)
In-Reply-To: <871c0cb0-5433-43db-a57c-aee96bdeae16@iscas.ac.cn>
On Thu, 10 Jul 2025, Jiawei wrote:
> In addition, can you provide a bug record or a reproduction method? I think
> it should also be fixed in the GCC community, and I will report the problems
> you encounter in test to GCC Bugzilla.
https://patchwork.ffmpeg.org/check/125495/
If you build ffmpeg with this patch, "make fate" fails on the monkeysaudio
tests, on loongarch. That's about as much as I have so far.
It should indeed be fixed in GCC. You can of course just report this
above, but with that only that info, it is somewhat unlikely that anybody
will tend to the bug and fix it. To make it properly actionable, you need
to isolate the code which gets miscompiled, so GCC developers can compile
and observe that the resulting code is wrong (which may require some
loongarch knowledge to see what is wrong) without needing to build and run
the full ffmpeg fate.
// Martin
_______________________________________________
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:[~2025-07-10 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250613083704.6858-1-jiawei@iscas.ac.cn>
2025-06-13 8:42 ` Martin Storsjö
2025-06-14 22:49 ` Michael Niedermayer
2025-06-16 7:37 ` Martin Storsjö
[not found] ` <a37b238c-c136-4a13-96ba-0bca77fdcb38@iscas.ac.cn>
[not found] ` <ec574b73-bf1d-4174-9e8f-617101a5820c@iscas.ac.cn>
2025-07-10 11:35 ` Martin Storsjö
[not found] ` <871c0cb0-5433-43db-a57c-aee96bdeae16@iscas.ac.cn>
2025-07-10 12:44 ` Martin Storsjö [this message]
2025-06-17 22:17 ` compn
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=fc22bc72-c4d7-7b53-ae50-1ff5fd02fbb@martin.st \
--to=martin@martin.st \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=jiawei@iscas.ac.cn \
/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