FWIW while MSVC may not support restrict, it supports __restrict [1], which
serves the same purpose. It would be straightforward to define a
macro MPICH_RESTRICT if you want to use that.
[1] https://docs.microsoft.com/en-us/cpp/cpp/extension-restrict?view=vs-2019
Jeff
On Thu, Aug 13, 2020 at 1:40 PM Raffenetti, Kenneth J. via devel <
devel(a)mpich.org> wrote:
> Hi everyone,
>
> Following a discussion today about C99 types in MPICH, we wanted to give a
> heads up. Since version 3.3, MPICH relies on many types which are
> technically optional in C99. For example uint64_t, uintptr_t, etc. In case
> it was not clear, platforms which do not provide these optional types are
> not supported by MPICH.
>
> The MPICH wiki page on C99 support has been updated to include this
> caveat: https://wiki.mpich.org/mpich/index.php/Shifting_toward_C99
>
> Please let us know if you have any questions, comments, or concerns.
>
> Thanks,
> Ken
>
> _______________________________________________
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/devel
>
--
Jeff Hammond
jeff.science(a)gmail.com
http://jeffhammond.github.io/
Hi everyone,
Following a discussion today about C99 types in MPICH, we wanted to give a heads up. Since version 3.3, MPICH relies on many types which are technically optional in C99. For example uint64_t, uintptr_t, etc. In case it was not clear, platforms which do not provide these optional types are not supported by MPICH.
The MPICH wiki page on C99 support has been updated to include this caveat: https://wiki.mpich.org/mpich/index.php/Shifting_toward_C99
Please let us know if you have any questions, comments, or concerns.
Thanks,
Ken
