|
| From: | Richard Henderson |
| Subject: | Re: [PATCH v6 77/82] target/arm: Fix decode for VDOT (indexed) |
| Date: | Sat, 15 May 2021 12:13:37 -0500 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 |
On 5/13/21 2:25 PM, Peter Maydell wrote:
-VDOT_scalar 1111 1110 0 . 10 .... .... 1101 . q:1 index:1 u:1 rm:4 \ - vm=%vm_dp vn=%vn_dp vd=%vd_dp +VDOT_scalar 1111 1110 0 . 10 .... .... 1101 . q:1 index:1 u:1 vm:4 \ + vn=%vn_dp vd=%vd_dpIs it possible to make this kind of bug a decodetree error? It seems unlikely that there's a use for having a bit which is decoded both by a %foo field specification and also in some other way...
That's not what's happening here. This has separate fields "rm" and "vm" decoded in different ways.
r~
| [Prev in Thread] | Current Thread | [Next in Thread] |