Build artifacts for riscv64#106
Merged
josephburnett merged 1 commit intojosephburnett:masterfrom Feb 22, 2026
Merged
Conversation
Co-authored by: [email protected]; Signed-off-by: ffgan <[email protected]>
Contributor
Author
Owner
|
Thanks @ffgan. Go has solid riscv64 support and this is a clean addition to the build targets. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
hi there.
Recently, riscv64 has gained widespread adoption, and we might consider adding riscv64 support to
jd. Go has excellent support for riscv64, so we only need minor modifications to enable building artifacts for riscv64.I ran
make buildon an riscv64 server, and the results show everything went smoothly.See details here, build.log
I noticed that I should run
make fuzz, but found that the results don't seem quite ideal. I also ran it on my x86 machine, but encountered errors as well. However, the x86 run in CI didn't report any errors, which is somewhat puzzling to me.See specific logs below
Nevertheless, I believe this should be unrelated to riscv64 and should also be unrelated to this PR, so I've deliberately ignored handling this error here.
So, if you have any questions about the above content, feel free to @ me directly anytime. I'm happy to answer all questions.
Other Info
Co-authored by: [email protected];