From: Michael Niedermayer <michael@niedermayer.cc>
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: Tue, 28 Nov 2023 15:21:55 +0100
Message-ID: <20231128142155.GN3543730@pb2> (raw)
In-Reply-To: <0F76AE61-2CCF-4397-BA9C-1C74AAD8BFEE@remlab.net>
[-- Attachment #1.1: Type: text/plain, Size: 1755 bytes --]
On Tue, Nov 28, 2023 at 09:27:08AM +0200, Rémi Denis-Courmont wrote:
>
>
> Le 28 novembre 2023 01:22:14 GMT+02:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
> >On Mon, Nov 27, 2023 at 05:46:40PM +0200, Rémi Denis-Courmont wrote:
> >[...]
> >> Also FWIW, RV broke due to misaligned accesses and illegal vector types that
> >> QEMU tolerated. That is rather an argument against QEMU than against this MR
> >> but still.
> >
> >has someone reported this to qemu ?
> >(seems like a bug)
>
> It's not a bug. The specification leaves those cases *undefined*. QEMU supports them because they can, and adding sanity checks would just slow stuff down.
>
> Also generally QEMU TCG policy seems to be maximize perf and compatibility, not formal correctness.
I think i read somewhere that recent qemu supposedly checks alignment on arm
more completely. But i couldnt quickly find a official statement about that
But either way, qemu could emit such code optionally when it is used for
testing. Which is one of the things people use qemu for.
So IMHO it would make sense for qemu to detect cases that are undefined
even if for no other reason than to emulate the hw more exactly.
If this is not done, qemu can be detected and code could refuse or
fail to run
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Modern terrorism, a quick summary: Need oil, start war with country that
has oil, kill hundread thousand in war. Let country fall into chaos,
be surprised about raise of fundamantalists. Drop more bombs, kill more
people, be surprised about them taking revenge and drop even more bombs
and strip your own citizens of their rights and freedoms. to be continued
[-- 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:[~2023-11-28 14:22 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ö
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 [this message]
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=20231128142155.GN3543730@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