Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] configure: Clearer documentation for "disable-safe-bitstream-reader"
Date: Fri, 11 Apr 2025 08:32:55 +0200
Message-ID: <GV1P250MB073772D581844374C47913578FB62@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250410170504.308400-1-michael@niedermayer.cc>

Michael Niedermayer:
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
>  configure | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/configure b/configure
> index bd4f8723760..f1db8b6f235 100755
> --- a/configure
> +++ b/configure
> @@ -436,7 +436,8 @@ Advanced options (experts only):
>    --enable-hardcoded-tables use hardcoded tables instead of runtime generation
>    --disable-safe-bitstream-reader
>                             disable buffer boundary checking in bitreaders
> -                           (faster, but may crash)
> +                           (This disables some security checks and can cause undefined behavior,
> +                            it may be faster, but should only be used with trusted input)
>    --sws-max-filter-size=N  the max filter size swscale uses [$sws_max_filter_size_default]
>  
>  Optimization options (experts only):

I'd like to keep "crash" in the description. Not everyone (not even
people setting "experts only" options) will be familiar with the term
"undefined behavior".

- Andreas

_______________________________________________
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:[~2025-04-11  6:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 17:05 Michael Niedermayer
2025-04-11  6:32 ` Andreas Rheinhardt [this message]
2025-04-12  0:11   ` Michael Niedermayer
2025-04-12  0:19     ` Timo Rothenpieler
2025-04-12  0:42       ` Michael Niedermayer
2025-04-16  0:34         ` Michael Niedermayer

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=GV1P250MB073772D581844374C47913578FB62@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.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