From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] enable auto vectorization for gcc 7 and higher
Date: Wed, 27 Jul 2022 19:49:41 +0200
Message-ID: <DB6PR0101MB22144BB3B3F60195D2432F8D8F979@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <d37a6879-3f05-5632-1bc8-eb9555a83755@gmail.com>
James Almer:
> On 7/27/2022 2:34 PM, Swinney, Jonathan wrote:
>> I recognize that this patch is going to be somewhat controversial. I'm
>> submitting it mostly to see what the opinions are and evaluate
>> options. I am working on improving performance for aarch64. On that
>> architecture, there are fewer hand written assembly implementations of
>> hot functions than there are for x86_64 and allowing gcc to
>> auto-vectorize yields noticeable improvements.
>>
>> Gcc vectorization has improved recently and it hasn't been evaluated
>> on the mailing list for a few years. This is the latest discussion I
>> found in my searches:
>> http://ffmpeg.org/pipermail/ffmpeg-devel/2016-May/193977.html
>
> Every time this was done, it was inevitably reverted after complains and
> crash reports started piling up because gcc can't really handle all the
> inline code our codebase has, among other things.
>
>>
>> If the community is not comfortable accepting a patch like this
>> outright, would you be willing to accept a new option to the configure
>> script, something like --enable-auto-vectorization?
>
> --extra-cflags can be used for this.
>
No, it can't, because what is given via --extra-cflags is inserted at
the start of CFLAGS, so that the automatically added -fno-tree-vectorize
overwrites it.
- Andreas
_______________________________________________
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:[~2022-07-27 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 17:34 Swinney, Jonathan
2022-07-27 17:39 ` James Almer
2022-07-27 17:49 ` Andreas Rheinhardt [this message]
2022-07-27 20:41 ` Hendrik Leppkes
2022-07-27 21:01 ` Martin Storsjö
2022-07-27 21:07 ` Hendrik Leppkes
2022-07-27 21:33 ` Andreas Rheinhardt
2022-07-28 1:02 ` Soft Works
2022-07-28 1:05 ` James Almer
2022-07-28 1:10 ` Soft Works
2022-07-28 1:15 ` Soft Works
2022-07-27 18:54 ` Soft Works
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=DB6PR0101MB22144BB3B3F60195D2432F8D8F979@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
--to=andreas.rheinhardt@outlook.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