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 2/2] sh4: remove architecture
Date: Thu, 13 Jun 2024 12:35:31 -0400
Message-ID: <CAPBf_Ono_1x6TjhUsTMsx1MGUbAYCF69X54+vTs5OptNLdC37A@mail.gmail.com> (raw)
In-Reply-To: <CAPBf_OmpPtmBy6Sbt0ACscod03wqsNJsriraSF6UoTpD4EA4Aw@mail.gmail.com>

On Fri, Jun 7, 2024, 17:18 Sean McGovern <gseanmcg@gmail.com> wrote:

> On Fri, Jun 7, 2024 at 2:20 PM Rémi Denis-Courmont <remi@remlab.net>
> wrote:
> >
> > Support for SuperH was dropped over a decade ago. There no longer is any
> > architecture-specific code to be found, so just remove the corresponding
> > test. Technically it is still possible to compile FFmpeg as the
> > "generic" (pure C) architecture.
> > ---
> >  configure             | 4 ----
> >  libavcodec/sh4/README | 6 ------
> >  2 files changed, 10 deletions(-)
> >  delete mode 100644 libavcodec/sh4/README
> >
> > diff --git a/configure b/configure
> > index 6c5b8aab9a..efead4075a 100755
> > --- a/configure
> > +++ b/configure
> > @@ -2146,7 +2146,6 @@ ARCH_LIST="
> >      ppc64
> >      riscv
> >      s390
> > -    sh4
> >      sparc
> >      sparc64
> >      tilegx
> > @@ -5249,9 +5248,6 @@ case "$arch" in
> >      s390|s390x)
> >          arch="s390"
> >      ;;
> > -    sh4|sh)
> > -        arch="sh4"
> > -    ;;
> >      sun4*|sparc*)
> >          arch="sparc"
> >      ;;
> > diff --git a/libavcodec/sh4/README b/libavcodec/sh4/README
> > deleted file mode 100644
> > index 8dd61fe875..0000000000
> > --- a/libavcodec/sh4/README
> > +++ /dev/null
> > @@ -1,6 +0,0 @@
> > -SH4 optimizations have been removed in
> > -commit d6096a67422534918405abb46dafbbac4608cbc3
> > -The last revission with the optimizations is
> cbfc9046e1c7e295b74f252902ae6f255eef4e78
> > -
> > -If you want to maintain these (or other) SH4 optimizations in ffmpeg,
> then please
> > -contact ffmpeg-devel@ffmpeg.org
> > --
> > 2.45.1
> >
> > _______________________________________________
> > 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".
>
> Sure, OK.
>

Also ping.

-- 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:[~2024-06-13 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 18:19 [FFmpeg-devel] [PATCH 1/2] lavu/bswap: remove some inline assembler Rémi Denis-Courmont
2024-06-07 18:19 ` [FFmpeg-devel] [PATCH 2/2] sh4: remove architecture Rémi Denis-Courmont
2024-06-07 21:18   ` Sean McGovern
2024-06-13 16:35     ` Sean McGovern [this message]
2024-06-07 21:17 ` [FFmpeg-devel] [PATCH 1/2] lavu/bswap: remove some inline assembler Sean McGovern
2024-06-11 13:15 ` Michael Niedermayer
2024-06-11 15:28   ` Rémi Denis-Courmont
2024-06-11 16:04     ` Michael Niedermayer
2024-06-11 16:27       ` Rémi Denis-Courmont
2024-06-11 15:38   ` James Almer
2024-06-11 15:50     ` Tomas Härdin
2024-06-11 16:10       ` Michael Niedermayer
2024-06-11 16:24         ` Rémi Denis-Courmont
2024-06-11 17:20         ` Tomas Härdin
2024-06-11 15:57     ` Michael Niedermayer
2024-06-11 15:59       ` Paul B Mahol
2024-06-11 16:08       ` James Almer
2024-06-11 16:17         ` Michael Niedermayer

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_Ono_1x6TjhUsTMsx1MGUbAYCF69X54+vTs5OptNLdC37A@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