From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/fate: advise on --assert-level=2
Date: Mon, 11 Mar 2024 21:45:30 +0100
Message-ID: <20240311204530.GT6420@pb2> (raw)
In-Reply-To: <20240311101606.1439795-2-nicolas.gaullier@cji.paris>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
On Mon, Mar 11, 2024 at 11:16:06AM +0100, Nicolas Gaullier wrote:
> Signed-off-by: Nicolas Gaullier <nicolas.gaullier@cji.paris>
> ---
> doc/fate.texi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/fate.texi b/doc/fate.texi
> index 2fa8c34c2d..2fa7c70251 100644
> --- a/doc/fate.texi
> +++ b/doc/fate.texi
> @@ -79,6 +79,13 @@ Do not put a '~' character in the samples path to indicate a home
> directory. Because of shell nuances, this will cause FATE to fail.
> @end float
>
> +Beware that some assertions are disabled by default, so mind setting
> +@option{--assert-level=<level>} at configuration time, e.g. when seeking
> +the highest possible test coverage:
> +@example
> +./configure --assert-level=2
> +@end example
This (or some other appropriate place in the docs)
should mention that doing so could have a performance impact
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-03-11 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 10:16 [FFmpeg-devel] [PATCH 0/1] " Nicolas Gaullier
2024-03-11 10:16 ` [FFmpeg-devel] [PATCH] " Nicolas Gaullier
2024-03-11 20:45 ` Michael Niedermayer [this message]
2024-03-12 12:09 Nicolas Gaullier
2024-03-18 15:05 ` Nicolas Gaullier
2024-03-19 2:36 ` 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=20240311204530.GT6420@pb2 \
--to=michael@niedermayer.cc \
--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