-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support for 32-bit architectures? #46
Comments
Hi I initially planned to support it. Thanks for reminding me I should work on this. It's a duplicate of |
Thank you! Closing to avoid duplicates. |
For reference, is it the project you are talking about? https://github.com/tillitis/tkeyclient |
Yes! I am packaging that for Debian now too. /Simon |
Fixes #6 Fixes #46 The tests in conversion_test.go are the ones that are not architecture dependent The tests in conversion_64bit_test.go complete them for 64-bit systems The tests in examples_test.go are the ones that are not architecture dependent The tests in examples_32bit_test.go are for 32-bit systems The tests in examples_64bit_test.go are for 64-bit systems The architecture dependent file covers the fact, you can reach a higher value with int and uint on 64-bit systems, but you will get a compile error on 32-bit. The error message is different on 32-bit and 64-bit systems The max is 9223372036854775807 on 64-bit and 2147483647 on 32-bit
Fixes #6 Fixes #46 The tests in conversion_test.go are the ones that are not architecture dependent The tests in conversion_64bit_test.go complete them for 64-bit systems The tests in examples_test.go are the ones that are not architecture dependent The tests in examples_32bit_test.go are for 32-bit systems The tests in examples_64bit_test.go are for 64-bit systems The architecture dependent file covers the fact, you can reach a higher value with int and uint on 64-bit systems, but you will get a compile error on 32-bit. The error message is different on 32-bit and 64-bit systems The max is 9223372036854775807 on 64-bit and 2147483647 on 32-bit
Fixes #6 Fixes #46 The tests in conversion_test.go are the ones that are not architecture dependent The tests in conversion_64bit_test.go complete them for 64-bit systems The tests in examples_test.go are the ones that are not architecture dependent The tests in examples_32bit_test.go are for 32-bit systems The tests in examples_64bit_test.go are for 64-bit systems The architecture dependent file covers the fact, you can reach a higher value with int and uint on 64-bit systems, but you will get a compile error on 32-bit. The error message is different on 32-bit and 64-bit systems The max is 9223372036854775807 on 64-bit and 2147483647 on 32-bit
Fixed with Confirmation #47 (comment) |
Hi. I'm packaging this for Debian (because the Tillitis TKEY has it as a dependency) and ran into a self test failure on i386:
https://salsa.debian.org/jas/golang-github-ccoveille-go-safecast/-/jobs/6578765
Could you fix this, so the package works on 32-bit platforms too? Or is this package only for 64-bit architectures?
/Simon
The text was updated successfully, but these errors were encountered: