https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86416
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> ---
First issue was:
lto1: fatal error: unsupported mode TF
Namely, a not that readable error message if a mode is not supported. (Here:
'complex(kind=16)' which is a float128-type complex number, which is only
supported on the host but not on the device (nvptx/Nvidia).)
[Side remark: The user intended complex*16 = complex(kind=8) = double-precision
complex.]
This now gives a message such as:
lto1: fatal error: nvptx-none - 128-bit-precision floating-point numbers
unsupported (mode 'TF')
Which is better readable. → FIXED by the commit r279528 of comment 8.
The second issue was:
CHARACTER default mapping didn't match the spec for 'scalar'
Well, OpenMP's terminology states that Fortran CHARACTER aren't scalars. Hence:
→ INVALID
As all issues are resolved, I close the bug. – Thanks for implicit suggestion
to improve the error message!
