about import_bits/export_bits about wide-integer HOT 9 CLOSED

After I change uintwide_t<1024U, std::uint32_t> to uintwide_t<1024U, std::uint8_t>
It's working

from wide-integer.

Hello @chriscp-cat I am investigating now.

At the moment, I am able to verify the correct import/export behavior for this data sample. These functions are, however, new. So a bit more testing might be in order.

I will cycle a few more tests and a dedicated pull request to verify the behavior.

Based on these results, I will try to analyze your example and see what's exactly going on.

from wide-integer.

I think there might be an issue with the chunk_size. Let me investigate more tomorrow and also see how my own tests run through?

Thanks for your query. I'bb return with more details in a day or so.

Kind regards, Chris

from wide-integer.

This is actually a bug regarding clearing the values of the output destination storage for export results. A fix will be available within a day or two. Many thanks for reporting this.

from wide-integer.

i have got it,Thanks for your work

from wide-integer.

This is a bug in the wide-integer code. I will also be fixing that and adding relevant test cases soon.

from wide-integer.

Teste for the repair are cycling in #317

from wide-integer.

Thank ypou @chriscp-cat for finding this and pointing it out. It is (or was) an actual bug. This should now be fixed in the main branch.

If you find similar issues or anything else needed here, please feel free report any findings.

from wide-integer.

Thanks,I think the problem has been solved

from wide-integer.