13:38:44 <hyc> hbs: yeah, we could shuffle the opcode assignments dynamically but it only requires a simple lookup table to deal with that
13:44:14 <sech1> And opcode shuffling will be dealt with by VLIW compiler anyway, if it's a VLIW architecture CPU. If it's ARM based, opcode shuffling won't do anything
14:06:16 <plowsof> Is this CFROUND tweak a response to someone using it already? Or just discovered / requires a fork and +10% for ryzen 0.1% for intel is fair? Or do ryzens already have a huge advantage?
15:18:27 <sech1> CFROUND is alreafy fast on Intel, but slow on Ryzen. I discovered it long time ago.