On Sat, 21 Oct 2017, Diego Biurrun wrote:
On Sat, Oct 21, 2017 at 12:04:48AM +0300, Martin Storsjo wrote:
The operand shouldn't be stored as is, but stored as 64-scale, in
the opcode, but armasm64 currently misses to do this.
This bug will be fixed in a future release, and a fix for the bug
will break the workaround. Therefore, only do the workaround as
long as a environment variable is set.
---
Suggestions on what to name the environment variable are welcome;
it's hard to guess what to name it as I don't know what version
the fix will appear in.
When do you expect this future release to appear? It may be sensible
to just wait for the fix to appear and live with a bit of pain in the
meantime...
I didn't get any estimate on that, but lately they've released fixes every
couple months, so it could possibly appear before the OS itself becomes
public.
// Martin
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
