Decoder fails to decode a few valid AMD instructions
See original GitHub issueWrong destination register, should be xmm1 but it’s xmm0
660F78C1A5FD
wrong: extrq xmm0, 0xa5, 0xfd
correct: extrq xmm1, 0xa5, 0xfd
W1 is allowed but xed can’t decode them:
8FE9F812C3 = llwpcb rbx
8FE9F812CB = slwpcb rbx
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Base64 decode error Last unit does not have enough valid bits
I open up cer_bundle.cer and see three certificates. First two seem fine. The final certificate when put thru Base64.getDecoder().decode(myCert) ...
Read more >How to decode a property with type… | Apple Developer Forums
Let's say I have. Customer data type which contains a metadata property that can contains any JSON dictionary in the customer object
Read more >How to interpret decode-error code for DM365 - TI E2E
Dear all: I get some error when decode H.264 as below: Bytes ... decoder not able to find valid NAL info. and 4...
Read more >Going Deep With Decodable - MartianCraft
Scenario 2: I want some decoding to be able to fail without bringing down the whole process, and without ending up with lots...
Read more >json — JSON encoder and decoder — Python 3.11.1 ...
This module does not comply with the RFC in a strict fashion, implementing some extensions that are valid JavaScript but not valid JSON....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
These two instructions are a little weird, the 2nd operand is always 32-bit according to the documentation, but xed shows it as a 64-bit register:
Jup, the destination register of
extrq
should be determined bymodrm.rm
instead ofmodrm.reg
, as the later one must be (is forced to) zero by definition.