[FFmpeg-devel] [PATCH] lavc/hevcdsp_qpel_neon: using movi.16b instead of movi.2d
徐福隆
839789740 at qq.com
Wed Nov 29 12:01:57 EET 2023
Thank you for your reading and explaining carefully, Martin.
Yes, you are right. I build with iOS 13.0, and FFmpeg 6.0.
It seems that there is no ".arch" directive in asm.S.
That is to say, it isn't a newest version.
------------------ Original ------------------
From: "FFmpeg development discussions and patches" <martin at martin.st>;
Date: Tue, Nov 28, 2023 09:57 PM
To: "xufuji456 via ffmpeg-devel"<ffmpeg-devel at ffmpeg.org>;
Cc: "徐福隆"<839789740 at qq.com>;
Subject: Re: [FFmpeg-devel] [PATCH] lavc/hevcdsp_qpel_neon: using movi.16b instead of movi.2d
Hi,
On Wed, 15 Nov 2023, xufuji456 via ffmpeg-devel wrote:
> Building iOS platform with arm64, the compiler has a warning:
> "instruction movi.2d with immediate #0 may not function correctly on
> this CPU, converting to movi.16b"
The change is correct and something we should do. However since
fb1b88af77cd39034cef4b6d08af79496cd75ed8, our asm.S starts with an ".arch"
directive, and that silences this warning, so I wonder how you've run into
it or tested it. (I presume you've run into it with an older version, then
tried to find all cases of this instruction in the codebase and changed
those?)
(This warning is something that only is triggered when building for iOS,
not macOS, due to a bug in early iPhone CPUs - see
https://github.com/llvm/llvm-project/commit/9097a07e4e83b9f394598d53557247277b064b09.)
Anyway, the change looks good, so I'll push it.
// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-devel
mailing list