04:01:47 <hyc> sech1: your v2 branch doesn't build on my lichee pi https://paste.debian.net/hidden/f0921546
04:02:32 <hyc> probably due to v0.7 vector support
06:18:24 <sech1> hyc it needs gcc-14 or newer
09:46:24 <hyc> ah I only have 13.2. lemme see if I can update
09:49:59 <hyc> how about clang?
10:07:29 <sech1> clang should work too. A recent version of course
10:13:58 <hyc> I'm using the installed gcc13 to build gcc14 from source. could be a while
13:26:25 <selsta> sech1: would the final version also require gcc 14? monero still supports gcc12 on master branch https://github.com/monero-project/monero/issues/9669
16:08:24 <sech1> selsta if you compile for risc-v - yes
16:08:46 <selsta> i missed the riscv context
16:08:50 <selsta> all good in this case
16:08:51 <sech1> But risc-v  boards generally have newer compilers because they're new
17:38:52 <m-relay> <g​ingeropolous:monero.social> any reason the benchmark would give me 6788.14, whereas xmrig gives me 9121.8 h/s?
17:40:29 <m-relay> <g​ingeropolous:monero.social> and i keep trying to justify buying one of these intel core ultra, but buying a dead socket is just..... bluh
17:53:34 <DataHoarder> benchmark with v2 tests different things, unless you are testing v1
17:54:31 <m-relay> <g​ingeropolous:monero.social> yeah those are v1 hashrates from the benchmark
17:58:30 <m-relay> <g​ingeropolous:monero.social> oh might be the wacky affinity for the 1920x
17:59:00 <DataHoarder> how many numa nodes for that? :D
17:59:18 <DataHoarder> can't remember if the benchmark cares about these and replicates dataset across each numa node
18:13:29 <m-relay> <g​ingeropolous:monero.social> well the --auto flag has interesting results. v1 = 7445.25 h/s, v2 = 7468.91 h/s.
18:14:33 <m-relay> <g​ingeropolous:monero.social> lulz nvm. v2 is 6715.3 . turns out -v2 not the same as --v2. who needs syntax checking anyways....
18:28:43 <sech1> Benchmark doesn't do numa
18:29:16 <sech1> You can set affinity, large pages, and enable msr mod via xmrig's script. But not numa