-
Notifications
You must be signed in to change notification settings - Fork 75
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
ARM64 support #131
Comments
For ARM CI, you may be able to leverage Docker by adding the qemu-arm-static binary to the image.
Image will then run natively on ARM and emulate ARM with qemu on x86. |
That'd be cool! And by CI you're talking about Travis? I'll see if we can manage Linux as well as ARM CI under one account (?) |
I'm not personally familiar with Travis. We use custom pipelines executing on our own servers at my job, so we have a lot more flexibility for customization. Just pointing out that you can run code on other architectures via Docker and qemu, in case it opens up some additional opportunities (easier than having separate hardware for each different architecture). |
Thanks, we can run docker on Travis. It'll be really nice to have a separate CI running for this |
@brev Moving here discussion from #134 (comment)
Fixing this type of errors should be relatively easy, as we define and use our types in Specifically about byte (from above Types.hpp):
@dkeeney we've discussed this, we do we need a signed byte? Ideally cross-platform would be std::byte. |
As far as I know it has always been a signed char. I have no reason for making it signed. But if we change it to unsigned then we may need to add some casts (or maybe remove some) in the places it is used. Personally I would prefer the unsigned char (std::byte) as being a Byte. |
from numenta#1439
Check if we can build on Arm64 too.
Should be easier, as ASM and platform specific code was mostly removed.
Thanks for testing when you have time, @paulscode
The text was updated successfully, but these errors were encountered: