You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following changes will resolve the issue and ensure that ForColormap is compatible with nvfortran. I hope that the issue will be resolved soon, but until then, it would be great to consider these changes:
Thanks @gha3mi, I have committed those fixes: b7e6154
We can let the issue open to revert these changes latter.
The 2nd and 4th are not really annoying, but the two with 222 are more annoying if we add more colourmaps and forget to update these numbers.
Hi @vmagnin
I've identified the issue with the
nvfortran
compiler and reported a simple example on the nvidia compiler forum:https://forums.developer.nvidia.com/t/nvfortran-f-0000-internal-compiler-error-module-new-dtype-dt-nfd/292240
The following changes will resolve the issue and ensure that ForColormap is compatible with nvfortran. I hope that the issue will be resolved soon, but until then, it would be great to consider these changes:
forcolormap/src/colormap_class.f90
Line 40 in 756be0f
to
character(*), dimension(6+222+4), public, parameter :: colormaps_list = &
forcolormap/src/miscellaneous_colormaps.f90
Line 35 in 756be0f
to
character(*), dimension(6), parameter, public :: miscellaneous_colormaps_list = &
forcolormap/src/miscellaneous_colormaps.f90
Line 35 in 756be0f
to
character(*), dimension(222), parameter, public :: scientific_colour_maps_list = &
forcolormap/src/matplotlib_colormaps.f90
Line 38 in 756be0f
to
character(*), dimension(4), parameter, public :: matplotlib_colormaps_list = &
The text was updated successfully, but these errors were encountered: