Sunday, 2022-11-13

*** lxo <lxo!~lxo@linux-libre.fsfla.org> has quit IRC04:35
*** lxo <lxo!~lxo@linux-libre.fsfla.org> has joined #libre-soc04:47
*** jab <jab!~jab@user/jab> has quit IRC06:33
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC08:43
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.41.167> has joined #libre-soc08:43
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.41.167> has quit IRC09:13
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has joined #libre-soc09:14
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC12:58
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.172.164> has joined #libre-soc13:03
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.172.164> has quit IRC13:30
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has joined #libre-soc13:38
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC16:30
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.172.135> has joined #libre-soc16:30
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.172.135> has quit IRC16:41
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.170.223> has joined #libre-soc16:42
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.170.223> has quit IRC16:55
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has joined #libre-soc16:55
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC16:59
*** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has joined #libre-soc17:00
*** ghostmansd <ghostmansd!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has joined #libre-soc17:04
ghostmansdlkcl, I have a question regarding failfirst mode for cr ops.17:07
ghostmansdfailfirst is also available for normal and ld/st imm modes.17:07
ghostmansdFor these, we set prefix.rm.mode[0, 1] to 0b01.17:08
ghostmansdHowever, CR ops don't seem to follow the same pattern.17:08
ghostmansdHere's what we have for (value, mask, field) entries:17:09
ghostmansd# normal17:09
ghostmansd(0b010001, 0b110001, "ffrc1"),  # ffirst,     Rc=117:09
ghostmansd(0b010000, 0b110001, "ffrc0"),  # ffirst,     Rc=017:09
ghostmansd# ld/st imm17:09
ghostmansd(0b010001, 0b110001, "ffrc1"),  # ffirst,     Rc=117:09
ghostmansd(0b010000, 0b110001, "ffrc0"),  # ffirst,     Rc=017:09
ghostmansd# crops17:09
ghostmansd(0b100001, 0b100001, "ff3"),    # ffist,      3-bit CR17:09
ghostmansd(0b100000, 0b100000, "ff5"),    # ffist,      5-bit CR17:09
ghostmansdFor normal and ld/st imm, value and mask patterns are created as `search = ((int(rm.mode) << 1) | Rc)`.17:10
ghostmansdI'd rather expect 0b010001 and 0b010000 for ff3 and ff5 respectively.17:23
ghostmansdIs this logic intentional?17:24
*** lxo <lxo!~lxo@linux-libre.fsfla.org> has quit IRC18:27
*** lxo <lxo!~lxo@linux-libre.fsfla.org> has joined #libre-soc18:38
ghostmansdlkcl, never mind, found the comment "# sigh, CROPs is different"19:08
lkclghostmansd, yes :)  you can't have a CR Field "co-result" (Rc=1) with an operation that creates... a CR Field21:01
lkclRc=1 says "is the 64-bit result greater, less, or equal to zero?"21:02
lkcland CR ops produce a 4-bit result, not a 64-bit result.21:02
lkcldoh :)21:02
*** ghostmansd <ghostmansd!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC22:34
*** lkcl <lkcl!lkcl@freebnc.bnc4you.xyz> has quit IRC22:36

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!