Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/vc2enc: Use LUT to assemble interleaved golomb, code
Date: Wed, 12 Mar 2025 14:46:34 +0100
Message-ID: <3869161c-d01b-4821-87e0-a9fbd2ae84fc@lynne.ee> (raw)
In-Reply-To: <GV1P250MB0737BCDD2DA697704E562CA78FD02@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>

On 12/03/2025 06:27, Andreas Rheinhardt wrote:
> Lynne:
>> On 12/03/2025 04:10, Andreas Rheinhardt wrote:
>>> Patches attached.
>>>
>>> - Andreas
>>
>> First patch is wild, its surprising no one considered inverting the way
>> decoder parses codes for an encoder yet.
> 
> I didn't even look at the decoder.
> (It is actually surprising that it took until
> 512e597932dfe05cf5665192efbe2c93c2e36af2 for the original code to be
> improved.)
> 
>> Rather than ORing and using put_bits63, I think it would make more sense
>> to write out each chunk using put_bits sequentially. It might be
>> possible to reverse the lookups such that you get the MSBs first so you
>> wouldn't need to reverse them out of place in a small array.
>> But either way, LGTM. Feel free to explore this in a follow-up.
> 
> I don't think that writing them sequentially will improve anything: In
> order to be able to use a LUT, I would have to shift the bits starting
> with the MSBs into position; and then there would be the internal shifts
> and checks inside put_bits().
> Apart from that: put_bits63() is the same as put_bits() when BUF_BITS is
> 64 (see ede2b391cc516f4f93621f6a214b3410b231f582).
> 
>>
>> Second patch seems a bit pointless. It's just one single call you're
>> uninlining? Chasing to save a few extra bytes of binary surely don't
>> deserve having a wrapper function for uninlining.
>>
> 
> I am uninlining all calls besides the hot one. 31 callsites.
> For GCC, this reduced codesize 2c36 to 25b1 (15% saved), for clang from
> 4b08 to 3338 (32% saved).

Oh, it was late and I didn't read carefully.
Both patches LGTM.
_______________________________________________
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-03-12 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  3:10 Andreas Rheinhardt
2025-03-12  4:50 ` Lynne
2025-03-12  5:27   ` Andreas Rheinhardt
2025-03-12 13:46     ` Lynne [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=3869161c-d01b-4821-87e0-a9fbd2ae84fc@lynne.ee \
    --to=dev@lynne.ee \
    --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