Skip to content
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

Enable the use of __uint128_t or uint64_t if available #4

Merged
merged 1 commit into from
Jun 10, 2024

Conversation

mrdcvlsc
Copy link
Owner

  • new macro directive for detecting if the type __uint128_t is available to be use as cast_t for 64-bit architectures

  • the same macro directive modifications aims to also detect the availability of the type uint64_t in 32-bit architectures to be use as cast_t

  • modified the workflow to force test programs to use limb_t of bit wideness 32 and 16

  • disable my old test header library's final test output and replace it with cmake's ctest

@mrdcvlsc mrdcvlsc force-pushed the use--uint128-t-if-available branch from 54dccaa to 5b20239 Compare June 10, 2024 08:11
- new macro directive for detecting if the type `__uint128_t` is available to be use as `cast_t` for 64-bit architectures

- the same macro directive modifications aims to also detect the availability of the type `uint64_t` in 32-bit architectures to be use as `cast_t`

- modified the workflow to force test programs to use `limb_t` of bit wideness 32 and 16

- disable my old test header library's final test output and replace it with cmake's ctest
@mrdcvlsc mrdcvlsc force-pushed the use--uint128-t-if-available branch from 5b20239 to 46e081d Compare June 10, 2024 08:22
@mrdcvlsc mrdcvlsc merged commit 6a1079d into main Jun 10, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant