Re: [FFmpeg-devel] [PATCH v3] gcc: Don't disable '-ftree-vectorize' if gcc version higher than 13.

Re: [FFmpeg-devel] [PATCH v3] gcc: Don't disable '-ftree-vectorize' if gcc version higher than 13.

[Martin Storsjö]

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.

// 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".

Re: [FFmpeg-devel] [PATCH v3] gcc: Don't disable '-ftree-vectorize' if gcc version higher than 13.

[Martin Storsjö]

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".