Henry Le Berre

Update: I looked into it some more today, intercepting the calls in Fortran and in C. Calling `zFORp_stream_set_execution`, the received arguments (in the Fortran interface) are correct but, when they...

@lindstro There is no need to apologize, thank you for responding. I had used [tests/fortran/testFortran.f](tests/fortran/testFortran.f) as a reference and do confirm it worked properly. However, adding a call to the...

@lindstro I agree, I don't think `c_ptrdiff_t` is the culprit. Thank you for taking a deeper look into this!

Thank you @lindstro for looking into this! As you mentioned, this is an issue with NVHPC, not with ZFP. We would all benefit from it being fixed on the compiler...

Thank you @jeffhammond for the clarification. I had replaced `ptrdiff_t` with a signed 64-bit integer but the arguments received by C had no resemblance to those passed in Fortran, even...

``` [Copying my message from the NVHPC forum channel] ``` Thank you very much **[MatColgrove](https://forums.developer.nvidia.com/u/MatColgrove)** and **[jeffhammond](https://github.com/jeffhammond)** for the clarification and help on this issue. I wasn't sure whether this...

What would you like to see in this file?

@sbryngelson What do you think about moving the contents of `m_precision_select` into `m_constants` ? I wonder how NVFortran will handle precision selection because we specify `-Mr8`: > -Mr8: (Fortran only)...

@lee-hyeoksu Do you expect a meaningful difference in output between current master and your branch for these test cases that fail? If so, you should regenerate the golden files for...

I am not sure if anyone uses Windows natively after I added support for it, but I do realize now that my PR #307 does not provide a way to...