From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/lpc: R-V V apply_welch_window
Date: Mon, 11 Dec 2023 12:03:16 +0200
Message-ID: <16C61DD4-CE18-4898-A7C3-A03D6368C146@remlab.net> (raw)
In-Reply-To: <170228867019.1197.13151450711414221625@lain.khirnov.net>
Le 11 décembre 2023 11:57:50 GMT+02:00, Anton Khirnov <anton@khirnov.net> a écrit :
>Quoting Rémi Denis-Courmont (2023-12-11 10:50:53)
>> Le 11 décembre 2023 11:11:28 GMT+02:00, Anton Khirnov <anton@khirnov.net> a écrit :
>> >I think it'd look a lot less like base64 < /dev/random if you vertically
>> >aligned the first operands.
>>
>> They are aligned to the 17th column. Problem is that quite a few vector mnemonics are larger than 7 characters.
>
>Align to 25 or 33 then?
IMO that's even worse. The operands end up too far off from most mnemonics that it hurts legibility more than it improves.
I initially aligned to the longest mnemonics but that turned out badly whenever revectoring (for obvious reasons).
>
>--
>Anton Khirnov
>_______________________________________________
>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".
_______________________________________________
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".
prev parent reply other threads:[~2023-12-11 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:46 Rémi Denis-Courmont
2023-12-11 9:11 ` Anton Khirnov
2023-12-11 9:50 ` Rémi Denis-Courmont
2023-12-11 9:57 ` Anton Khirnov
2023-12-11 10:03 ` Rémi Denis-Courmont [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=16C61DD4-CE18-4898-A7C3-A03D6368C146@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