Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] enable auto vectorization for gcc 7 and higher
Date: Wed, 27 Jul 2022 18:54:36 +0000
Message-ID: <DM8P223MB0365F48175DBBC2473B415E3BA979@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <05a46152f1b2458ea326edd9cfb6d817@amazon.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Swinney, Jonathan
> Sent: Wednesday, July 27, 2022 7:35 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] [PATCH] enable auto vectorization for gcc 7
> and higher
> 
> 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
> 
> 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?
> 
> Thanks!
> 
> Signed-off-by: Jonathan Swinney <jswinney@amazon.com>
> ---
>  configure | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/configure b/configure
> index 6629d14099..c63c9348ad 100755
> --- a/configure
> +++ b/configure
> @@ -7173,7 +7173,9 @@ if enabled icc; then
>              disable aligned_stack
>      fi
>  elif enabled gcc; then
> -    check_optflags -fno-tree-vectorize
> +    case $gcc_basever in
> +        2|2.*|3.*|4.*|5.*|6.*) check_optflags -fno-tree-vectorize ;;
> +    esac
>      check_cflags -Werror=format-security
>      check_cflags -Werror=implicit-function-declaration
>      check_cflags -Werror=missing-prototypes
> --

LGTM - basically. I had removed that flag about two years ago and never
seen an issue (Win,Linux,BSD x x86_64,armv7,aarch64). 
But it has always been with quite recent versions of gcc, so I can't say 
whether it's safe already with 7.x

One exception I've seen was with an Android NDK build in gcc compatibility
mode, where I got a clang compilation error. But that's nothing of concern
I think.

sw




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

      parent reply	other threads:[~2022-07-27 18:54 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
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 [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=DM8P223MB0365F48175DBBC2473B415E3BA979@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.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