Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] configure: permit POWER9 cpu flags
Date: Sat, 13 Jul 2024 11:46:14 +0300
Message-ID: <2274798.xIjfq26nYX@basile.remlab.net> (raw)
In-Reply-To: <20240704012330.2046242-1-gseanmcg@gmail.com>

Le torstaina 4. heinäkuuta 2024, 4.23.29 EEST Sean McGovern a écrit :
> ---
>  configure | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/configure b/configure
> index b28221f258..bbda7a02cb 100755
> --- a/configure
> +++ b/configure
> @@ -5493,7 +5493,7 @@ elif enabled ppc; then
>              cpuflags="-mcpu=$cpu"
>              disable vsx
>          ;;
> -        power[7-8]*)
> +        power[7-9]*)
>              cpuflags="-mcpu=$cpu"
>          ;;
>          cell)

IMO, the CPU should just be passed as, well, CPU by default - like AArch64 
already does. PPC does not have that many CPU types. But generally speaking, 
keeping up with all CPU model names that GCC and Clang seems like a very vain 
and fruitless exercise.

Of course we can keep special case matching for *existing* special values that 
FFmpeg has historically accepted, but lets maybe stop adding new ones?

-- 
レミ・デニ-クールモン
http://www.remlab.net/



_______________________________________________
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:[~2024-07-13  8:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  1:23 Sean McGovern
2024-07-04  1:23 ` [FFmpeg-devel] [PATCH 2/2] lavc/flacdsp: implement wasted32 DSP function for VSX on POWER Sean McGovern
2024-07-04 11:15   ` Rémi Denis-Courmont
2024-07-04 16:26     ` Sean McGovern
2024-07-04 17:45       ` Rémi Denis-Courmont
2024-07-06 20:00         ` Sean McGovern
2024-07-06 20:17           ` Rémi Denis-Courmont
2024-07-07 16:51             ` Sean McGovern
2024-07-07 18:21   ` [FFmpeg-devel] [PATCH] " Sean McGovern
2024-07-13  8:51     ` Rémi Denis-Courmont
2024-07-06 19:56 ` [FFmpeg-devel] [PATCH 1/2] configure: permit POWER9 cpu flags Sean McGovern
2024-07-12 21:09 ` Sean McGovern
2024-07-13  8:46 ` Rémi Denis-Courmont [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=2274798.xIjfq26nYX@basile.remlab.net \
    --to=remi@remlab.net \
    --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