RA = 0x7ffffffff CA = 1 result in simulation is that CA=1 but CA32=0 to be resolved: is this a simulator bug or is it an HDL error
I can add this to power-instruction-analyzer
simulator bug commit 1fc2a159a3181ac77fe7156de7ca811d185548f9 resolved by special-casing OP_ADD
commit f3b4db25993b9be457c0c0b87d2bfea78a83a247 (HEAD -> master) Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net> Date: Thu Aug 27 20:52:58 2020 +0100 xer so is not being passed through to CR0 another one in "addme."
(In reply to Jacob Lifshay from comment #1) > I can add this to power-instruction-analyzer yes please, it's really quite frustrating, the sheer number of options.
commit 9486ce5933b5a20031166a1caffa0821b2af883f (HEAD -> master, origin/master) Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net> Date: Thu Aug 27 21:18:12 2020 +0100 https://bugs.libre-soc.org/show_bug.cgi?id=476 XER SO not being "listened" to correctly when OE=0 and Rc=1 creating CR0 jacob this was another (arbitrary) test, coming from microwatt: lst = ["addme. 6, 16"] initial_regs = [0] * 32 initial_regs[16] = 0x7ffffffff initial_sprs = {} xer = SelectableInt(0, 64) xer[XER_bits['CA']] = 1 xer[XER_bits['SO']] = 1