Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] tx_float_neon: Do not access outside stack.
Date: Sun, 09 Oct 2022 17:11:04 +0300
Message-ID: <2648779.mvXUDI8C0e@basile.remlab.net> (raw)
In-Reply-To: <20221009131447.5001-1-Reimar.Doeffinger@gmx.de>

Le sunnuntaina 9. lokakuuta 2022, 16.14.47 EEST Reimar Döffinger a écrit :
> Use load/store instructions that modify sp to save
> registers to stack, like it is done for all other
> functions.
> At least valgrind complains about the current code.
> ---
>  libavutil/aarch64/tx_float_neon.S | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/libavutil/aarch64/tx_float_neon.S
> b/libavutil/aarch64/tx_float_neon.S index 4126c3b812..4be93cc963 100644
> --- a/libavutil/aarch64/tx_float_neon.S
> +++ b/libavutil/aarch64/tx_float_neon.S
> @@ -866,10 +866,10 @@ FFT16_FN ns_float, 1
> 
>  .macro FFT32_FN name, no_perm
>  function ff_tx_fft32_\name\()_neon, export=1
> -        stp             d8,  d9,  [sp, #-16]
> -        stp             d10, d11, [sp, #-32]
> -        stp             d12, d13, [sp, #-48]
> -        stp             d14, d15, [sp, #-64]
> +        stp             d8,  d9,  [sp, #-16]!
> +        stp             d10, d11, [sp, #-16]!
> +        stp             d12, d13, [sp, #-16]!
> +        stp             d14, d15, [sp, #-16]!

While this fixes the ABI violation, it introduces multiple data dependencies on 
stack pointer due to write-back.

The idiomatic way to do this is to allocate the entire needed stack space in 
the first store / last load, and use positive offsets elsewhence.

> 
>          LOAD_SUBADD
>          SETUP_SR_RECOMB 32, x7, x8, x9
> @@ -911,10 +911,10 @@ function ff_tx_fft32_\name\()_neon, export=1
>          zip2            v31.2d, v11.2d, v15.2d
>          st1             { v28.4s, v29.4s, v30.4s, v31.4s }, [x1]
> 
> -        ldp             d14, d15, [sp, #-64]
> -        ldp             d12, d13, [sp, #-48]
> -        ldp             d10, d11, [sp, #-32]
> -        ldp             d8,  d9,  [sp, #-16]
> +        ldp             d14, d15, [sp], #16
> +        ldp             d12, d13, [sp], #16
> +        ldp             d10, d11, [sp], #16
> +        ldp             d8,  d9,  [sp], #16
> 
>          ret
>  endfunc


-- 
Rémi Denis-Courmont
http://www.remlab.net/



_______________________________________________
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:[~2022-10-09 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 13:14 Reimar Döffinger
2022-10-09 14:11 ` Rémi Denis-Courmont [this message]
2022-10-09 16:36   ` Reimar Döffinger
2022-10-09 16:54     ` Rémi Denis-Courmont

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=2648779.mvXUDI8C0e@basile.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