Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Sean McGovern <gseanmcg@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libpostproc: remove big-endian AltiVec acceleration
Date: Thu, 10 Apr 2025 08:47:12 -0400
Message-ID: <CAPBf_O=M+3bqs-U6dqqdD5wiVtckgqMaS7YRTJiLp+YAF-2Hgg@mail.gmail.com> (raw)
In-Reply-To: <GV1P250MB07375D7835F2258A7D7D94568FB72@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>

Hi Andreas,

On Thu, Apr 10, 2025, 03:37 Andreas Rheinhardt <
andreas.rheinhardt@outlook.com> wrote:

> Sean McGovern:
> > Hi,
> >
> > On Wed, Apr 9, 2025 at 2:55 PM Michael Niedermayer
> > <michael@niedermayer.cc> wrote:
> >>
> >> 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
> >>
> >
> > We already discovered a few months back that we have no real
> > maintainers for these ppc pieces, so as noted in the ticket I am
> > working on removing them.
>
> unmaintained != broken
>

This statement was neither expressed nor implied from the patch.


> > Is this what you want in the patch notes?
> >
> >> Also you are changing public API without version bump
> >>
> >
> > Oops, yeah OK I can do that.
> > Is a minor bump enough or should this be a major?
>
> This would need a proper deprecation period.
> (You can also deprecate the 3DNOW define at the same time.


OK sure, will update and send later.

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

-- Sean McGovern

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

      reply	other threads:[~2025-04-10 12:47 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
2025-04-10  1:30   ` Sean McGovern
2025-04-10  7:37     ` Andreas Rheinhardt
2025-04-10 12:47       ` Sean McGovern [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='CAPBf_O=M+3bqs-U6dqqdD5wiVtckgqMaS7YRTJiLp+YAF-2Hgg@mail.gmail.com' \
    --to=gseanmcg@gmail.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