Hi Jiaxing, > Here is the table. It does not say what I told you it said, so the > retraction comes first.
Thank you for the table, and for leading with the retraction. The replacement is worth more than the sentence it replaces: 364 of 364 with a single register partitioning the two groups one to one is a field with a reason, even if what selects the arm is still open. The third value is the honest kind of catch too - a row that breaks the lockstep and narrows the claim to the regular datapath instead of being averaged into it. > The script that produces every number in it is small enough to > send if you want to re-run it against your own corpus. Yes, please send it. One honest note first: there is no vendor .rknn on this disk - everything on my RK3588 side is upstream Mesa and generated TFLite, and the script reads .rknn. So the run worth doing from here is the axis your corpus cannot test: all 94 of your files carry the same 2.3.2 build string, and I will try to collect files produced by other toolkit versions and point the script at those. If 34/66 <-> 0x4044 holds across versions, that is one more thing RESERVED_0 is not. On v11: the clocks patch carried exactly as sent, authorship chain intact. Thank you for doing that carefully. Igor
