From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avr32: remove explicit support
Date: Mon, 10 Jun 2024 14:27:23 +0300 (EEST)
Message-ID: <9d4edf3-54a8-f365-316a-804c1a55ce9@martin.st> (raw)
In-Reply-To: <20240609115510.1371263-1-remi@remlab.net>
On Sun, 9 Jun 2024, Rémi Denis-Courmont wrote:
> The vendor has long since switched to Arm, wit the last product reaching
> their official end-of-life over 11 years ago. Linux support for the ISA
> was dropped 7 years ago. More importantly, this architecture was never
> supported by upstream GCC, and the vendor fork is stuck at version 4.2,
> which FFmpeg no longer supports (as per C11 requirement).
>
> Presumably, this is still the case given the lack of vendor support.
> Indeed all of the code being removed here consisted of inline assembler
> scalar optimisations. A sane C compiler should be able to perform those
> automatically nowadays (with the sole exception of fast CLZ detection),
> but this is moot as this architecture is evidently dead.
> ---
> configure | 26 +----
> libavcodec/avr32/mathops.h | 101 ------------------
> libavcodec/mathops.h | 2 -
> libavutil/avr32/bswap.h | 44 --------
> libavutil/avr32/intreadwrite.h | 182 ---------------------------------
> libavutil/bswap.h | 2 -
> libavutil/intreadwrite.h | 2 -
> 7 files changed, 1 insertion(+), 358 deletions(-)
> delete mode 100644 libavcodec/avr32/mathops.h
> delete mode 100644 libavutil/avr32/bswap.h
> delete mode 100644 libavutil/avr32/intreadwrite.h
LGTM
// Martin
_______________________________________________
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".
next prev parent reply other threads:[~2024-06-10 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 11:55 Rémi Denis-Courmont
2024-06-10 11:27 ` Martin Storsjö [this message]
2024-06-14 20:06 ` Tomas Härdin
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=9d4edf3-54a8-f365-316a-804c1a55ce9@martin.st \
--to=martin@martin.st \
--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