From: "Martin Storsjö" <martin@martin.st>
To: Jiawei <jiawei@iscas.ac.cn>
Cc: michael@niedermayer.cc, george@nsup.org,
kieran618@googlemail.com, remi@remlab.net, post@frankplowman.com,
quinkblack@foxmail.com, ffmpeg-devel@ffmpeg.org,
andreas.rheinhardt@outlook.com
Subject: Re: [FFmpeg-devel] [PATCH v3] gcc: Don't disable '-ftree-vectorize' if gcc version higher than 13.
Date: Thu, 12 Jun 2025 14:11:33 +0300 (EEST)
Message-ID: <19444a95-4c7c-ee43-491e-1b1bdbdd02b@martin.st> (raw)
In-Reply-To: <cd2fd8d2-efa1-b41e-1581-f14883782ef1@martin.st>
On Thu, 12 Jun 2025, Martin Storsjö wrote:
> On Thu, 12 Jun 2025, Jiawei wrote:
>
>> This patch modifies the FFmpeg build system to allow gcc use
>> '-ftree-vectorize'
>> option in newer releases.
>>
>> Modern GCC versions can be benefit when using the `-ftree-vectorize` flag.
>> Through it can optimizations in loop analysis and SIMD code generation.
>>
>> Version log:
>> Only allow GCC versions >= 13 to use -ftree-vectorize.
>> Modify the commit description.
>>
>> Disscussion see:
>> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20250521061750.54882-1-jiawei@iscas.ac.cn/
>>
>
> Thanks for removing the somewhat misleading references to AVX, SVE and RVV.
>
> But please do include the references to the earlier reverted attempt at
> reenabling this - that is key to why this may work better now than it did
> last time.
And to make it clear: The commit message itself really should contain this
information, it's not enough to reference information elsewhere on
patchwork/ML archives for such essential parts of the change.
// 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".
prev parent reply other threads:[~2025-06-12 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250612104645.8990-1-jiawei@iscas.ac.cn>
2025-06-12 11:08 ` Martin Storsjö
2025-06-12 11:11 ` Martin Storsjö [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=19444a95-4c7c-ee43-491e-1b1bdbdd02b@martin.st \
--to=martin@martin.st \
--cc=andreas.rheinhardt@outlook.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=george@nsup.org \
--cc=jiawei@iscas.ac.cn \
--cc=kieran618@googlemail.com \
--cc=michael@niedermayer.cc \
--cc=post@frankplowman.com \
--cc=quinkblack@foxmail.com \
--cc=remi@remlab.net \
/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