Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libpostproc: remove big-endian AltiVec acceleration
Date: Wed, 9 Apr 2025 20:55:39 +0200
Message-ID: <20250409185539.GZ4991@pb2> (raw)
In-Reply-To: <20250406164230.2030945-1-gseanmcg@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1864 bytes --]

Hi Sean

On Sun, Apr 06, 2025 at 12:42:30PM -0400, Sean McGovern wrote:
> While POWER & PowerPC systems have technically
> supported little-endian from inception,
> it did not come into proper usage until the
> introducion of the POWER8 in 2013.
> 
> The AltiVec acceleration present here has not
> had meaningful change since before then.
> 
> refs: Trac/11120
> ---
>  libpostproc/postprocess.c                  |   13 -
>  libpostproc/postprocess.h                  |    1 -
>  libpostproc/postprocess_altivec_template.c | 1211 --------------------
>  libpostproc/postprocess_template.c         |   31 -
>  4 files changed, 1256 deletions(-)
>  delete mode 100644 libpostproc/postprocess_altivec_template.c

What exactly are you fixing here / what is the problem?
You say the code hasnt been changed and you link to a ticket
where people cant decide if they talk about big or little endian
and that links to seemingly unrelated tickets

Please clearly explain what the issue is and why this is
the correct fix

Also you are changing public API without version bump

[...]
> index 5decb7e8a9..a88fd5a5cb 100644
> --- a/libpostproc/postprocess.h
> +++ b/libpostproc/postprocess.h
> @@ -88,7 +88,6 @@ void pp_free_context(pp_context *ppContext);
>  #define PP_CPU_CAPS_MMX   0x80000000
>  #define PP_CPU_CAPS_MMX2  0x20000000
>  #define PP_CPU_CAPS_3DNOW 0x40000000
> -#define PP_CPU_CAPS_ALTIVEC 0x10000000
>  #define PP_CPU_CAPS_AUTO  0x00080000
>  
>  #define PP_FORMAT         0x00000008

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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:[~2025-04-09 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-06 16:42 Sean McGovern
2025-04-09 14:45 ` Sean McGovern
2025-04-09 18:55 ` Michael Niedermayer [this message]
2025-04-10  1:30   ` Sean McGovern
2025-04-10  7:37     ` Andreas Rheinhardt
2025-04-10 12:47       ` Sean McGovern

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=20250409185539.GZ4991@pb2 \
    --to=michael@niedermayer.cc \
    --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