Re: [FFmpeg-devel] [PATCH] arm32/neon: Avoid using bge/beq for function calls

2023-01-14 Thread Martin Storsjö
Hi Rui, On Sat, 14 Jan 2023, Rui Ueyama wrote: On Sat, 7 Jan 2023, Rui Ueyama wrote: 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 han

Re: [FFmpeg-devel] [PATCH] arm32/neon: Avoid using bge/beq for function calls

2023-01-13 Thread Rui Ueyama
Hey Martin, It's nice to see you on this mailing list! Sorry about sending this email as a reply to a wrong email, as I didn't receive your mail and thus couldn't send this as a reply to your mail. > On Sat, 7 Jan 2023, Rui Ueyama wrote: > > > It looks like compiler-generated code always uses `b

Re: [FFmpeg-devel] [PATCH] arm32/neon: Avoid using bge/beq for function calls

2023-01-09 Thread Martin Storsjö
On Mon, 9 Jan 2023, Martin Storsjö wrote: Hi Rui, Long time no see! On Sat, 7 Jan 2023, Rui Ueyama wrote: 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 P

Re: [FFmpeg-devel] [PATCH] arm32/neon: Avoid using bge/beq for function calls

2023-01-09 Thread Martin Storsjö
Hi Rui, Long time no see! On Sat, 7 Jan 2023, Rui Ueyama wrote: 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 cod