From: "Rémi Denis-Courmont" <remi@remlab.net>
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 19:27:19 +0300
Message-ID: <3421885.8Q9FGFJ40s@basile.remlab.net> (raw)
In-Reply-To: <20240611160417.GM2821752@pb2>
Le tiistaina 11. kesäkuuta 2024, 19.04.17 EEST Michael Niedermayer a écrit :
> then simply remove avr32 with that explanation (no C11 compiler, and any
> other reason)
No. Måns and my optimisation arguments stand, even if it is purely
hypothetical in the case of AVR32 (for which there is no working compiler). It
is a *general* argument.
Removing the AVR32 support is not the point of *this* patch, so you are asking
me to misrepresent what the patch does and why. As for SH4, James already
addressed that.
> but if a commit message says the code is removed because that "allows for
> better optimisations" then yes i ask for benchmarks
"Allows for better optimisations" means exactly that: enable compilers to
*potentially* optimise better. I never claimed that it actually improved
performance in any given particular case.
Nevertheless it will make performance worse in one and only one case: a
defective/half-baked compiler: missing the byte-swap instruction (if it
exists) and/or a proper scheduling model, for the target. In other words, you
are essentially arguing that FFmpeg should be optimised for bad C compilers
instead of good ones.
--
雷米‧德尼-库尔蒙
http://www.remlab.net/
_______________________________________________
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-11 16:27 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 [this message]
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=3421885.8Q9FGFJ40s@basile.remlab.net \
--to=remi@remlab.net \
--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