From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3 2/2] swscale/aarch64: add hscale specializations
Date: Fri, 27 May 2022 00:00:23 +0300 (EEST)
Message-ID: <5e208810-bd84-b48d-7aba-32d2eec624c1@martin.st> (raw)
In-Reply-To: <A49E3847-F7C0-495C-85B9-4BFE9B38AD11@itanimul.li>
On Thu, 26 May 2022, J. Dekker wrote:
>> +
>> + // gather random access data from src into contiguous memory
>> + ldr w8, [x3, w8, UXTW] // src[filterPos[idx + 0]][0..3]
> Current asm code has lowercase uxtw, would prefer to keep it consistent.
>> + ldr w9, [x3, w9, UXTW] // src[filterPos[idx + 1]][0..3]
>> + ldr w10, [x3, w10, UXTW] // src[filterPos[idx + 2]][0..3]
>> + ldr w11, [x3, w11, UXTW] // src[filterPos[idx + 3]][0..3]
>> + ldr w12, [x3, w12, UXTW] // src[filterPos[idx + 4]][0..3]
>> + ldr w13, [x3, w13, UXTW] // src[filterPos[idx + 5]][0..3]
>> + ldr w14, [x3, w14, UXTW] // src[filterPos[idx + 6]][0..3]
>> + ldr w15, [x3, w15, UXTW] // src[filterPos[idx + 7]][0..3]
>> + stp w8, w9, [sp] // *scratch_mem = { src[filterPos[idx + 0]][0..3], src[filterPos[idx + 1]][0..3] }
>> + stp w10, w11, [sp, #8] // *scratch_mem = { src[filterPos[idx + 2]][0..3], src[filterPos[idx + 3]][0..3] }
>> + stp w12, w13, [sp, #16] // *scratch_mem = { src[filterPos[idx + 4]][0..3], src[filterPos[idx + 5]][0..3] }
>> + stp w14, w15, [sp, #24] // *scratch_mem = { src[filterPos[idx + 6]][0..3], src[filterPos[idx + 7]][0..3] }
>> +
>> +1:
>> + ld4 {v16.8B, v17.8B, v18.8B, v19.8B}, [sp] // transpose 8 bytes each from src into 4 registers
> Same with format specifiers being lower case, i.e. v16.8b
That's indeed the convention for most of our code, but we do have some
amount of code using uppercase for these too. In particular, this file
itself uses uppercase for such things so far.
Ideally we would reformat those files to use consistent styles, but until
then I don't have a very strong opinion about it (we can add it matching
the surrounding code and then reformat it all later, or add the new code
in the generally preferred style).
// 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:[~2022-05-26 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 2:02 Swinney, Jonathan
2022-05-26 10:58 ` J. Dekker
2022-05-26 21:00 ` Martin Storsjö [this message]
2022-05-27 19:47 ` Swinney, Jonathan
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=5e208810-bd84-b48d-7aba-32d2eec624c1@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