No Branch/Tag Specified
arm
asyncnotedecryption
danger
dev
dev-aarch64
dev-mac
dev-old-randomx
divzaddrs
dragonx
duke
freebsd
getfilterednotes
hip39
insync
jahway603
master
mvstuff
onryo
p2p_privacy
ramhash
relaytx
rx-largepages
setbestchain
warmup
witness_cache
wolfssl
wolfssl_win
z_createrawtransaction
z_importwallet
z_signmessage
v0.11.2.z0
v0.11.2.z1
v0.11.2.z2
v0.11.2.z3
v0.11.2.z4
v0.11.2.z5
v0.11.2.z6
v0.11.2.z7
v0.11.2.z8
v0.11.2.z9
v1.0.0
v1.0.0-beta1
v1.0.0-beta2
v1.0.0-rc1
v1.0.0-rc2
v1.0.0-rc3
v1.0.0-rc4
v1.0.1
v1.0.10
v1.0.10-1
v1.0.11
v1.0.11-rc1
v1.0.12
v1.0.12-rc1
v1.0.13
v1.0.13-rc1
v1.0.13-rc2
v1.0.14
v1.0.14-rc1
v1.0.15
v1.0.15-rc1
v1.0.2
v1.0.3
v1.0.4
v1.0.5
v1.0.6
v1.0.7-1
v1.0.8
v1.0.8-1
v1.0.9
v1.1.0
v1.1.0-rc1
v1.1.1
v1.1.1-rc1
v1.1.1-rc2
v1.1.2
v1.1.2-rc1
v2.0.0
v2.0.0-rc1
v2.0.1
v3.0.0
v3.1.0
v3.1.1
v3.10.0
v3.10.1
v3.10.2
v3.2.0
v3.2.1
v3.2.1-alpha
v3.2.1-beta
v3.2.2
v3.2.3
v3.3.0
v3.3.1
v3.3.2
v3.4.0
v3.4.1
v3.5.0
v3.5.1
v3.5.2
v3.6.0
v3.6.1
v3.6.2
v3.6.3
v3.7.0
v3.7.1
v3.8.0
v3.9.0
v3.9.1
v3.9.2
v3.9.3
v3.9.4
Labels
bounty up to 500 HUSH 2001-5000 bounty
bounty between 2001 and 5000 HUSH 501-2000 bounty
bounty between 501 and 2000 HUSH arm
something doesn't work on arm beginners
for new developers bug
may or may not be a bug build
problems building documentation
not enough information feature
new feature high priority
high priority i2p
related to i2p low priority
low priority medium priority
medium priority question
something is not clear release
release label or issue related to it testing
related to testing tor
related to tor wontfix
this won't be fixed
Apply labels
Clear labels
0-500 bounty
bounty up to 500 HUSH 2001-5000 bounty
bounty between 2001 and 5000 HUSH 501-2000 bounty
bounty between 501 and 2000 HUSH arm
something doesn't work on arm beginners
for new developers bug
may or may not be a bug build
problems building documentation
not enough information feature
new feature high priority
high priority i2p
related to i2p low priority
low priority medium priority
medium priority question
something is not clear release
release label or issue related to it testing
related to testing tor
related to tor wontfix
this won't be fixed
No Label
0-500 bounty
2001-5000 bounty
501-2000 bounty
arm
beginners
bug
build
documentation
feature
high priority
i2p
low priority
medium priority
question
release
testing
tor
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
This issue currently doesn't have any dependencies.
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
https://gcc.gnu.org/gcc-13/changes.html
And it blows up on
gcc (GCC) 13.1.1 20230429
on Artix Linux (would most likely be the same on Arch Linux). Log file is attached.@jahway603 looks like it gets pretty far and then gets an error compiling the RandomX tests. You may want to submit this as a bug to RandomX upstream, it's likely they haven't tested on gcc13 yet :
We may also want to avoid compiling the RandomX tests (which would be a way around this issue for us) because they are never run.
Where are the RandomX tests in the code so I can disable to test?
Made new gcc13 branch test this.
@jahway603 have you read the RandomX docs and/or source code to see if there is a way to not compile the tests? Also, have you reported this bug to RandomX devs? It's best if they fix the bug in their own repo.
@duke I'm unable to find how to disable the RandomX tests. I have filed Issue https://github.com/tevador/RandomX/issues/267 with the RandomX devs.
They have fixed their code. We should update to the latest version of the RandomX code.
I see they fixed their code in https://github.com/tevador/RandomX/pull/268, but I don't how to update our code to the latest RandomX version.
@jahway603 on the dev branch, copy their source code into the src/RandomX subdirectory of the hush3 git repo, then commit the result. We should write docs for this somewhere. This will likely pull in other changes but we likely want those as well. Also, in theory, their code changes should not cause consensus changes, but it's an extremely good idea to verify that by making sure their latest code is still able to mine blocks on DRGX mainnet.
@jahway603 also, please document the commit id of RandomX that is being used in the commit message, similar to
36140a5457
. Also, looking at that commit reminded me that I removed the audits/ subdirectory of RandomX because it contains many large files we don't need.I've attempted building hushd with just the one line change from upstream in the dev branch, and it failed. Log will be in a different repo.
I then attempted building hushd with other changes from upstream, including the recent one changed line in the gcc13 branch, and it failed. Log will be in a different repo.
Hushd now successfully builds with gcc13 as per commit
121ec4b9d4
What's next for testing this?
@jahway603 making sure that a dragonx full node can stay in sync and mine a block on the latest dev code
@jahway603 have you been able to test randomx mining on the latest dev code? If not, maybe ask the community and outsource the testing
@duke I have not been able to do further testing. I'm the only person I know with gcc13 on any OSes.
@jahway603 you can compile a new binary on the dev branch and then get others to test it. We want to test the new dev branch with dragonx mining, testing it on gcc13 is optional
I am actually going to close this issue, since it's no longer about gcc13, it's about making sure the new dev branch is still compatible with dragonx mainnet. I will make a new issue for that