Hi Paul,

I'm not sure if you have extra time.
But I think you are correct. We might need to report the bug to ffmpeg.

I'm not sure if we can simplify the test.
Like just run "ffplay test_raw.avi" or "ffmpeg -i test_raw.avi out.mp4" to see if it has the bus error as well.

Yours,
Paul

Paul Gevers 於 2022/4/6 02:52 寫道:
Hi,

On 04-04-2022 23:11, Ying-Chun Liu (PaulLiu) wrote:
It is because your environment supports "neon" and ffmpeg will use that for acceleration.

I wonder.

But abel and qemu-user-static doesn't support neon.
I think if you "cat /proc/cpuinfo" and neon will be in the Features.

root@ci-worker-armel-01:~# cat /proc/cpuinfo | grep neon
root@ci-worker-armel-01:~#

Nope.

Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

I now notice that the list of flags is also in the gdb output. If anything, it more looks like ffmpeg *thinks* it can use neon, but can't. Would that be a bug in ffmpeg?

I'll see if I can use cpuflags in ffmpeg to disable neon on my test. So that it can pass.

Ack, but I wonder if the bug needs to be cloned an reassigned to ffmpeg then, for detecting neon when not available.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to