Include ORC in neonv8 machine definition #675
Merged
Conversation
This file contains 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
Signed-off-by: Clayton Smith <[email protected]>
|
CI logs show that neonv8 kernels are now executing on aarch64. The test failure is unrelated; it's due to #676. |
Alesha72003
pushed a commit
to Alesha72003/volk
that referenced
this pull request
May 15, 2024
Include ORC in neonv8 machine definition
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I noticed that neonv8 kernels do not run in CI, nor do they run on my Raspberry Pi if
liborc-0.4-devis installed. It looks like this happens because VOLK chooses theneon_orcmachine over the ORC-lessneonv8machine.The
neonv8machine is the only one inmachines.xmlthat lacksorc|; adding this corrects the problem, and VOLK then chooses theneonv8_orcmachine and executes neonv8 kernels.