Internal compiler error detected when building the project about toml-f

[awvwgk]

An ICE is always a bug in the compiler, please report this to the Intel team (checkout https://fortran-lang.discourse.group/t/4929).

[awvwgk]

Might actually be a valid issue flagged at

toml-f/src/tomlf/datetime.f90

Line 144 in d7b892b

if (all([string(first+3:first+3), string(first+6:first+6)] == ":") &

where the second condition has to be checked first to prevent out-of-bounds access.

[han190]

Thank you for the link! It seems that the ICE is related with the "Advanced use of character expressions, constructor" discussed in the thread.

[awvwgk]

Is this still an issue with the latest 2023.1 release?

[han190]

Hi, I just downloaded the newest version and the project can be built without any problem, but when running fpm test --compiler ifx, I get the following error

forrtl: severe (408): fort: (4): Variable STRING has substring ending point 14 which is greater than the variable length of 10

Image              PC                Routine            Line        Source
tftest             000000000047D03A  new_datetime_from         144  datetime.f90
tftest             00000000004F2266  extract_datetime         1390  lexer.f90
tftest             0000000000452AB8  token_datetime           1177  lexer.f90
tftest             0000000000503959  run_unittest              400  testdrive.F90
tftest             0000000000502DD2  run_testsuite             344  testdrive.F90
tftest             000000000040702D  tftester                   67  main.f90
tftest             000000000040523D  Unknown               Unknown  Unknown
libc.so.6          00007F93F1B4E510  Unknown               Unknown  Unknown
libc.so.6          00007F93F1B4E5C9  __libc_start_main     Unknown  Unknown
tftest             0000000000405155  Unknown               Unknown  Unknown
<ERROR> Execution for object " tftest " returned exit code  152
<ERROR>*cmd_run*:stopping due to failed executions
STOP 152

which is not an ICE. So, I guess we could close this issue and open a new issue instead?