-
UkoeHBFinally `[==========] 4 tests from 1 test suite ran. (116923 ms total) [ PASSED ] 4 tests.` @rbrunner7 your prayers against mind-melting bugs failed, but the tests run now.
-
br-m<jeffro256> @tevador Thank you
-
tevador@jeffro256: Is is possible to undo the X3 -> T3 change here? tevador/mx25519 #15/changes#diff-f88320d20cbcadcd31e31556981049044269fff801ef8bc28a66c83d39b0919a
-
br-m<chaser> @DataHoarder: "can you export that into gh pages or something...?" it's a cheat, but it works: html-preview.github.io/?url=https:/…/blob/master/fcmp%2B%2B-carrot.html
-
DataHoarderhacky, works :)
-
DataHoarderwhere in that planner is testnet (not stressnet release/activation
-
DataHoarder?
-
DataHoarderor is that implicit/derived from the target date
-
br-m<jeffro256> I just haven't added it yet
-
br-m<jeffro256> I'd assume that it would be soon after the HF activation merge
-
br-m<jeffro256> Maybe one month
-
br-m<jeffro256> One question is whether the 6 month wait period should be after the HF activation code merge, or one after the one month code freeze post-merge
-
br-m<jeffro256> The latter would shave one month off the timeline, but I think both purposed are still served well
-
sech1wait period is there to let users update their nodes, miners, and maybe some custom code. Mostly the miners and custom code - nodes can be updated much quicker. So 6 months after the code is finalized (except for bugfixes)
-
sech1XMRig with RandomX v2 support was released on Mar 28th, so it's been 4 months already
-
br-m<jeffro256> @tevador, I'm looking into it right now. Yeah the results are very pronounced on my Intel i7-1355U, it's like a 7.5% slowdown
-
br-m<jeffro256> Which, it's only doing like 0.5% extra compute, so yeah definitely smells like a memory dependency issue
-
tevadorIt looks like the _unclamped arm64 code is broken
-
tevadorIs referenceBlock verification implemented somewhere? Seems to be missing here: monero-project/monero #9436