Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
29310 Discussions

ifx 2024.2.1 gives me a compile error #6068

hmatsuo
Novice
883 Views

The environment is Windows 64-bit.
Test code and compilation results are attached.

Summary of results.
  ifx 2024.2.1 Build 20240711 error #6068
  ifort 2021.13.1 Build 20240703_000000 error #6068
  ifort 19.0.4.245 Build 20190417 OK

I know how to change the code and not get a compile error,
but I want to create an object file without changing the code.
Because there are a lot of things that need to be changed.

I'd like to know if there are any compile options in ifx that do'nt cause compililation errors.

Labels (1)
0 Kudos
4 Replies
andrew_4619
Honored Contributor III
869 Views

There are no attachments!

0 Kudos
hmatsuo
Novice
818 Views

I'm sorry. I forgot to attach it.
Source and compile logs attached.

The compilation batch is as follows:
----
rem ifx
ifx /Qm64 /c /Od /traceback /warn:declarations /warn /Qsave /GS /nogen-interfaces T6068.f
rem ifort
ifort /Qm64 /c /Od /traceback /warn:declarations /warn /Qsave /GS /nogen-interfaces T6068.f
----

andrew_4619
Honored Contributor III
780 Views

OK your code is wrong, the older compiler did not detect but it still worked OK. We can see why that would be so. I know of no compiler option that would make that OK, maybe there is one I do not known about but I doubt it. It would be strange for a vendor to create an option to allow non-conforming code in the absence of a clearly defined vendor extension.

I see two options::

1] Revert to an old compiler and wait for the day when there is no computer or Operating system available to support it and then fix or abandon the code.

2] Fix the code and move on.

Sorry to be the bearer of bad news.

 

 

hmatsuo
Novice
767 Views

Thank you very much for your answer.
There doesn't seem to be a compiler option that avoids the error.

There's a lot of code that needs to be changed, so we'll figure out what to do.

0 Kudos
Reply