From: Rui Ueyama <rui314@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH] arm32/neon: Avoid using bge/beq for function calls Date: Sat, 7 Jan 2023 11:54:24 +0800 Message-ID: <CACKH++YDMtFrb7eMf__D=yXkVjHDZ_P6aC1qawCqUX6XMaJO6Q@mail.gmail.com> (raw) It looks like compiler-generated code always uses `b`, `bl` or `blx` instructions for function calls. These instructions have a 24-bit immediate and therefore can jump anywhere between PC +- 16 MiB. This hand-written assembly code instead uses `bge` and `beq` for interprocedural jumps. Since these instructions have only a 19-bit immediate (we have less bits for condition code), they can jump only within PC +- 512 KiB. This sometimes causes a "relocation R_ARM_THM_JUMP19 out of range" error when linked with the mold linker. This error can easily be avoided by using `b` instead of `bge` or `beq`. Signed-off-by: Rui Ueyama <rui314@gmail.com> --- libswresample/arm/audio_convert_neon.S | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/libswresample/arm/audio_convert_neon.S b/libswresample/arm/audio_convert_neon.S index 085d50aafa..3fe114772c 100644 --- a/libswresample/arm/audio_convert_neon.S +++ b/libswresample/arm/audio_convert_neon.S @@ -133,12 +133,13 @@ endfunc function swri_oldapi_conv_fltp_to_s16_nch_neon, export=1 cmp r3, #2 - itt lt - ldrlt r1, [r1] - blt .L_swri_oldapi_conv_flt_to_s16_neon - beq .L_swri_oldapi_conv_fltp_to_s16_2ch_neon + bgt 2f + beq 1f + ldr r1, [r1] + b .L_swri_oldapi_conv_flt_to_s16_neon +1: b .L_swri_oldapi_conv_fltp_to_s16_2ch_neon - push {r4-r8, lr} +2: push {r4-r8, lr} cmp r3, #4 lsl r12, r3, #1 blt 4f -- 2.34.1 _______________________________________________ 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 reply other threads:[~2023-01-07 3:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-07 3:54 Rui Ueyama [this message] 2023-01-09 16:01 ` Martin Storsjö 2023-01-09 21:48 ` Martin Storsjö 2023-01-14 4:08 ` Rui Ueyama 2023-01-14 22:30 ` Martin Storsjö
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='CACKH++YDMtFrb7eMf__D=yXkVjHDZ_P6aC1qawCqUX6XMaJO6Q@mail.gmail.com' \ --to=rui314@gmail.com \ --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