-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARROW-17440: [C++] Support RISC-V architecture #13902
Conversation
|
Did a quick test on x86 host with qemu and riscv ubuntu image. |
Signed-off-by: Felix Yan <felixonmars@archlinux.org>
else() | ||
set(ARROW_CPU_FLAG "x86") | ||
message(FATAL_ERROR "Unknown system processor") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we want to be open-ended instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
message(FATAL_ERROR "Unknown system processor") | |
message(WARNING "Unknown system processor") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My concern is if some patterns are missed in MATCHES list, CPU specific settings below may be skipped accidentally if user doesn't notice the message, e.g, without enabling SIMD flags.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, fair enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @felixonmars and @cyb70289 !
Benchmark runs are scheduled for baseline = 9d1bbaf and contender = 050876c. 050876c is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
MemoryAdviseWillNeed is passing here on VisionFive v1 development board. However, I got multiple failures in arrow-flight-test like:
Retried a few times ending up with different subset of the test suite failing. I'm testing against arrow 8.0.1 though, not sure if they are already fixed. |
@felixonmars Would be nice if you could test with git master. If the failure still occurs there, feel free to open a JIRA :-) |
- LTO is disabled for similar reason as #1620 - The `-DARROW_CPU_FLAG=riscv64` is no longer needed in a future version containing apache/arrow#13902 - Added to qemu-user-blacklist because QEMU doesn't support madvise(WILLNEED) properly (this includes qemu-system, actually) - `nocheck` is needed for now as `arrow-flight-test` is failing with the current version but not on git master. Recheck on next release!
- LTO is disabled for similar reason as #1620 - The `-DARROW_CPU_FLAG=riscv64` is no longer needed in a future version containing apache/arrow#13902 - Added to qemu-user-blacklist because QEMU doesn't support madvise(WILLNEED) properly (this includes qemu-system, actually) - `nocheck` is needed for now as `arrow-flight-test` is failing with the current version but not on git master. Recheck on next release!
Signed-off-by: Felix Yan <felixonmars@archlinux.org> Lead-authored-by: Yibo Cai <yibo.cai@arm.com> Co-authored-by: Felix Yan <felixonmars@archlinux.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
Signed-off-by: Felix Yan felixonmars@archlinux.org