13:07:00 <sech1> "Rounding: Valgrind does observe the 4 IEEE-mandated rounding modes (to nearest, to +infinity, to -infinity, to zero) for the following conversions: float to integer, integer to float where there is a possibility of loss of precision, and float-to-float rounding. For all other FP operations, only the IEEE default mode (round to nearest) is
13:07:00 <sech1> supported."
13:07:13 <sech1> RIP my attempts to run any RandomX using code under valgrind
13:08:05 <sech1> hyc have you ever tried using valgrind with RandomX in monerod or anywhere else?
17:38:44 <hyc> no, never tried it.
17:39:06 <hyc> sech1 what are you trying to test?
17:46:59 <sech1> Trying to run P2Pool with valgrind. It works only without RandomX
17:47:22 <sech1> With RandomX, it just doesn't sync. It doesn't even spit out "invalid hash" errors
18:09:22 <hyc> so you suspect memory corruption bugs somewhere?
18:10:20 <hyc> maybe try with ElectricFence. but as I recall, there are no plain uses of heap allocations, everything is using mmap'd memory. so efence wouldn't find anything.
18:21:58 <sech1> No, there is no memory corruption. Valgrind just doesn't support rounding modes (except for float <-> int conversions)
18:24:14 <sech1> I wanted to try it to see what it finds. It works fine without RandomX (and it didn't find anything)