From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] avutil/mem: limit alignment to maximum simd align
Date: Sun, 11 Feb 2024 16:22:26 +0200
Message-ID: <28944831.M1oAu7xOKb@basile.remlab.net> (raw)
In-Reply-To: <48f7655d-6311-49df-b813-c0acc9031142@rothenpieler.org>
Le perjantaina 9. helmikuuta 2024, 21.22.17 EET Timo Rothenpieler a écrit :
> On 13.01.2024 16:46, Timo Rothenpieler wrote:
> > FFmpeg has instances of DECLARE_ALIGNED(32, ...) in a lot of structs,
> > which then end up heap-allocated.
> > By declaring any variable in a struct, or tree of structs, to be 32 byte
> > aligned, it allows the compiler to safely assume the entire struct
> > itself is also 32 byte aligned.
> >
> > This might make the compiler emit code which straight up crashes or
> > misbehaves in other ways, and at least in one instances is now
> > documented to actually do (see ticket 10549 on trac).
> > The issue there is that an unrelated variable in SingleChannelElement is
> > declared to have an alignment of 32 bytes. So if the compiler does a copy
> > in decode_cpe() with avx instructions, but ffmpeg is built with
> > --disable-avx, this results in a crash, since the memory is only 16 byte
> > aligned.
> >
> > Mind you, even if the compiler does not emit avx instructions, the code
> > is still invalid and could misbehave. It just happens not to. Declaring
> > any variable in a struct with a 32 byte alignment promises 32 byte
> > alignment of the whole struct to the compiler.
> >
> > This patch limits the maximum alignment to the maximum possible simd
> > alignment according to configure.
> > While not perfect, it at the very least gets rid of a lot of UB, by
> > matching up the maximum DECLARE_ALIGNED value with the alignment of heap
> > allocations done by lavu.
> > ---
> >
> > libavutil/mem.c | 8 +++++++-
> > libavutil/mem_internal.h | 14 ++++++++------
> > 2 files changed, 15 insertions(+), 7 deletions(-)
> >
> > diff --git a/libavutil/mem.c b/libavutil/mem.c
> > index 36b8940a0c..b5bcaab164 100644
> > --- a/libavutil/mem.c
> > +++ b/libavutil/mem.c
> > @@ -62,7 +62,13 @@ void free(void *ptr);
> >
> > #endif /* MALLOC_PREFIX */
> >
> > -#define ALIGN (HAVE_AVX512 ? 64 : (HAVE_AVX ? 32 : 16))
> > +#if defined(_MSC_VER)
> > +/* MSVC does not support conditionally limiting alignment.
> > + Set minimum value here to maximum used throughout the codebase. */
> > +#define ALIGN (HAVE_SIMD_ALIGN_64 ? 64 : 32)
Not that I care whatsoever, but are we assuming that MSVC supports only x86?
Otherwise, this conditional definition does not make much sense and seems very
sketchy. In fact, I don't see the point in making this distinction at all
(*unlike* below).
--
レミ・デニ-クールモン
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".
next prev parent reply other threads:[~2024-02-11 14:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 20:10 [FFmpeg-devel] [PATCH] avutil/mem: always align by at least 32 bytes Timo Rothenpieler
2023-12-06 12:27 ` Timo Rothenpieler
2023-12-06 12:31 ` James Almer
2023-12-06 12:56 ` Timo Rothenpieler
2023-12-06 12:50 ` Ronald S. Bultje
2023-12-06 12:54 ` James Almer
2023-12-06 13:25 ` Martin Storsjö
2023-12-06 13:27 ` Timo Rothenpieler
2023-12-06 13:29 ` Martin Storsjö
2023-12-08 0:15 ` Timo Rothenpieler
2023-12-08 5:57 ` Martin Storsjö
2023-12-08 10:01 ` Andreas Rheinhardt
2023-12-08 17:56 ` Timo Rothenpieler
2023-12-08 18:11 ` Nicolas George
2023-12-09 5:23 ` Andreas Rheinhardt
2024-01-12 23:10 ` Timo Rothenpieler
2024-01-13 0:57 ` [FFmpeg-devel] [PATCH] avutil/mem: limit alignment to maximum simg align Timo Rothenpieler
2024-01-13 1:00 ` Timo Rothenpieler
2024-01-13 15:24 ` Timo Rothenpieler
2024-01-13 15:46 ` [FFmpeg-devel] [PATCH v2] avutil/mem: limit alignment to maximum simd align Timo Rothenpieler
2024-02-09 19:22 ` Timo Rothenpieler
2024-02-11 14:05 ` Sam James
2024-02-11 14:22 ` Rémi Denis-Courmont [this message]
2024-02-11 15:47 ` Timo Rothenpieler
2024-02-11 14:00 ` Andreas Rheinhardt
2024-02-11 16:06 ` Timo Rothenpieler
2024-02-11 17:40 ` [FFmpeg-devel] [PATCH] " Timo Rothenpieler
2024-02-26 16:58 ` Timo Rothenpieler
2024-02-27 18:45 ` Timo Rothenpieler
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=28944831.M1oAu7xOKb@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