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-requ...@ffmpeg.org with subject "unsubscribe".
