Exposing limb type choice by introducing _ZL
and _ZLL
#48
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.
Hello Niek, first of all thanks for writing
ctbignum
-- such a great and useful library.I'm using
ctbignum
for writing code, which I'm offloading to GPU. I noticed when converting literal input tostd::integer_sequence
, default limb type choice isuint64_t
, which is somewhat problematic to me. As I was trying to target SPIRV, which not supporting__uint128_t
so I was getting errors when writing GPU kernels which were performing modular multiplication.Also I noticed your question
I've introduced
_ZL
and_ZLL
-- these two new literal suffixes, while deprecating_Z
. I'd love to know your opinion/ suggestion.Thanks :)