On 5/29/24 06:32, Peter Maydell wrote:
We do plenty of other treatments of UNPREDICTABLE as UNDEF (e.g. STREX). Why is this case any different?It just seems like a lot of effort to go to. Sometimes we UNDEF for UNPREDICTABLEs, but quite often we say "the behaviour we get for free is fine, so no need to write extra code". In this particular case, also: * we'd need to go back and cross-check against older architecture manuals and also look at whether M-profile and A-profile are doing the same thing here * the "v8 loosens the UNPREDICTABLE case for m = 13 T1 encoding" looks suspiciously to me like a "nobody ever actually made this do anything except behave like the A1 encoding, so make T1 and A1 the same" kind of relaxation Basically, it would take me probably 15+ minutes to review the changes against the various versions of the docs and I don't think it's worth the effort :-)
Fair enough. I've sent a patch to update thumb.risu to avoid the problematic patterns. r~
