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 on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Compability issues with F66

HC_I_
Beginner
‎11-12-2015 08:20 AM
483 Views

Hello, I'm trying to compile some sources coded that come from Unisys basic mode with F66 compatibility. I have create the makefile with the flags -f66 -nowarn, but I got a lot of syntax issues related to types, initialization, use of pseudo-functions,...etc. Maybe the reason of that is because I'm not using the right flags, so please could anyone give me any advise or help me with it?

Thanks in advance!

 

 

0 Kudos

Link Copied

1 Reply
TimP
Honored Contributor III
‎11-12-2015 08:30 AM
483 Views

The -f66 flag is not well adapted to Unisys extensions from Fortran 66.   It is designed to allow IBM style f66 + extensions to work.  If you want advice, you will need to show some representative examples.  If the code was designed to work only with the Unisys compiler and depend on a 36-bit word size, it may be rather difficult.  I've never seen a compiler for other than a 18/36-bit machine which was designed to support such extensions, even by setting flags.

In short, your problem most likely is that your source code is not Fortran 66, so setting flags for some incompatible dialect of f66 isn't likely to help.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.