From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fate.sh: Allow overriding what targets to make for running the tests
Date: Thu, 30 Nov 2023 13:05:37 +0200 (EET)
Message-ID: <3815eb5a-b143-3e27-945c-b114bf9af15a@martin.st> (raw)
In-Reply-To: <cf3d3f6c-a290-7d61-24a6-28fc33e62cf1@martin.st>
On Mon, 27 Nov 2023, Martin Storsjö wrote:
> Anyway, the concrete case I'm considering, is that we've got AArch64 code
> merged, that uses the I8MM extensions. We don't have any FATE configuration
> that continuously test that. Whenever there are patches, I do spin up a cloud
> instance that supports this extension and test the patches there, but
> inbetween that we're pretty much blind.
>
> While checkasm's coverage isn't fantastic, for this particular case I'm not
> merging any AArch64 code for new extensions unless that code is covered by
> checkasm.
>
> The other AArch64 feature that we do have code for, which also is untested,
> is the assembly support for branch protection and pointer authentication.
> Also this is testable pretty easily with QEMU. It's of course more
> interesting to run the full fate suite, but if we're not looking for bugs in
> the compiler but only for bugs in our assembly, then checkasm should cover
> most of it.
So if you don't mind, I'd like to go ahead and push this, and set up those
instances so that we do get some continuous testing of the corners of our
aarch64 assembly that we otherwise only test occasionally.
// Martin
_______________________________________________
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:[~2023-11-30 11:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 12:31 Martin Storsjö
2023-11-27 15:46 ` Rémi Denis-Courmont
2023-11-27 21:55 ` Martin Storsjö
2023-11-30 11:05 ` Martin Storsjö [this message]
2023-11-30 14:23 ` Rémi Denis-Courmont
2023-11-30 15:34 ` Martin Storsjö
2023-11-30 16:03 ` Rémi Denis-Courmont
2023-11-30 16:28 ` Martin Storsjö
2023-11-30 17:37 ` Rémi Denis-Courmont
2023-11-30 21:13 ` Martin Storsjö
2023-12-01 7:36 ` Rémi Denis-Courmont
2023-12-01 7:55 ` Martin Storsjö
2023-12-01 12:06 ` Rémi Denis-Courmont
2023-11-27 22:10 ` Alexander Strasser
2023-11-27 23:22 ` Michael Niedermayer
2023-11-28 7:27 ` Rémi Denis-Courmont
2023-11-28 14:21 ` Michael Niedermayer
2023-11-30 15:52 ` 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=3815eb5a-b143-3e27-945c-b114bf9af15a@martin.st \
--to=martin@martin.st \
--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