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 1/2] lavu/bswap: remove some inline assembler
Date: Tue, 11 Jun 2024 17:57:21 +0200
Message-ID: <20240611155721.GL2821752@pb2> (raw)
In-Reply-To: <f088cfa5-5897-4dc4-ab9f-a07f928a8f5a@gmail.com>


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

On Tue, Jun 11, 2024 at 12:38:37PM -0300, James Almer wrote:
> On 6/11/2024 10:15 AM, Michael Niedermayer wrote:
> > On Fri, Jun 07, 2024 at 09:19:46PM +0300, Rémi Denis-Courmont wrote:
> > > C code or compiler built-ins are preferable over inline assembler for
> > > byte-swaps as it allows for better optimisations (e.g. instruction
> > > scheduling) which would otherwise be impossible.
> > > 
> > > As with f64c2e710fa1a7b59753224e717f57c48462076f for x86 and Arm,
> > > this removes the inline assembler on GCC (and Clang) since we now
> > > require recent enough compiler versions (this indeed seems to work on
> > > AArch64).
> > > ---
> > >   libavutil/aarch64/bswap.h | 56 ---------------------------------------
> > >   libavutil/avr32/bswap.h   | 44 ------------------------------
> > >   libavutil/bswap.h         |  8 +-----
> > >   libavutil/sh4/bswap.h     | 48 ---------------------------------
> > 
> > As you are writing that this preferrable for better optimisations
> > Please provide benchmarks (for sh4, avr32)
> 
> This is a ridiculous request, considering nobody has such hardware at all.

Then I think its a ridiculous claim that this optimizes the code

I mean, at some point there was hardware and these optimisations did improve
speed.

This patch is not removing the code because its a rare (or dead) platform, it removes
it with the claim that this would "allows for better optimisations"
Iam sorry but i do not see why asking for the claim in the commit message
to be backed up with facts being ridiculous
The claim in the commit message may be ridiculous

thx

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

No great genius has ever existed without some touch of madness. -- Aristotle

[-- 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:[~2024-06-11 15:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 18:19 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
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 [this message]
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=20240611155721.GL2821752@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