Intel Software Network articles feed

Fortran READ returns iostat=98 error

Fri, 30 Oct 2009 13:24:23 -0700

When the Fortran READ statement returns iostat=98 the error message is, "cannot allocate memory for the file buffer - out of memory". This error is caused by the runtime library attempting to create a buffer large enough to hold the output of the read. This will happen for unformatted files opened for sequential access. This error can be seen, for example, on a Windows XP, 32-bit system when attempting to read from virtual memory if the pagefile is set too small. This error can affect any operating system, though 32-bit platforms are more likely to hit it.

There are several ways to work around this error. One option is making more virtual memory available by increasing the pagefile size on the system where you are running the application. If you have control over the file creation, and don’t require a record structure to the file, adding ACCESS=’STREAM’ to the OPEN for both the file creation and use will usually avoid this problem. For more details on stream access, see the compiler documentation topic ‘File Access and File Structure’.

Parallel Debugger Extension Exceptions: 0xa1a01db1, 0xa1a01db2

Tue, 08 Sep 2009 10:39:53 -0700

Problem :
Running Openmp code under the VS 2005 debugger displays the following unexplained exceptions:
First-chance exception at 0x7c812afb in Parallel_bug.exe: 0xA1A01DB1: 0xa1a01db1.
First-chance exception at 0x7c812afb in Parallel_bug.exe: 0xA1A01DB2: 0xa1a01db2.

Environment :
Compiler Professional Edition 11.1 (Fortran), Microsoft Visual Studio 2005, IA-32 or Intel 64.

Root Cause :
These exceptions are used to initiate communication between the run-time library and the parallel debugger add-in. In VS2008 (and later) they are handled silently, however, there is a known limitation with VS2005 that requires these exceptions to be enabled manually, otherwise, they are reported by the debugger. This information had been left out of the ifort 11.1 release notes, but should be included for 11.1 update 2.

Resolution :
Manually set up VS 2005 to break on these exceptions by going to Debug>Exceptions...>Win32 Exceptions and enabling Intel Parallel Extension Exceptions 0, 1 and 2. This will cause the exceptions to be handled silently

Error 6405 with interface checking and EXTERNAL declaration in module

Mon, 31 Aug 2009 13:36:12 -0700

Reference Number : DPD200139304

Version : 11.1

Operating System : All

Problem Description : The compiler will incorrectly issue diagnostic 6405: The same named entity from different modules and/or program units cannot be referenced, in the following situation:

A procedure (subroutine or function) is declared with an implicit interface (just a type and/or EXTERNAL) in a module.
A program unit USEs the module and calls the procedure twice or more.
The application is compiled with the generated interface checking feature enabled. (From the command line, the option /warn:interface (Windows) or -warn interface (Linux and Mac OS X); in the Visual Studio development environment, property Fortran > Diagnostics > Check Routine Interfaces is set to Yes.)

Example:

module MYMOD
logical, external :: func
end module MYMOD

program MAIN
use MYMOD
print *, FUNC(0)
print *, FUNC(1)
end program MAIN

Resolution Status : This error will be corrected in a future product version. The simplest workaround is to recode the declaration in the module as an INTERFACE block. For example:

module MYMOD
interface
logical function FUNC (ARG)
integer, intent(IN) :: ARG
end function FUNC
end interface
end module MYMOD

If the procedure is written in Fortran, a preferable alternative is to place it in the module as a module procedure. This avoids the need to write a separate declaration of the procedure, but does require that any caller USE the module.

For information on other causes of this error, see Diagnostic 6405: The same named entity from different modules and/or program units cannot be referenced.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Troubleshooting Fortran Integration Issues with Visual Studio

Fri, 14 Aug 2009 12:03:52 -0700

This article describes diagnostic and repair steps to follow if Intel Visual Fortran integration into Microsoft Visual Studio is not working correctly.

The symptoms of errors with Fortran integration into Visual Studio include:

When opening a Fortran project, an error indicating that the .vfproj project file is not recognized
Missing Fortran-specific parts of the Visual Studio interface, such as project templates or project properties
Inability to build a Fortran project

This article applies to Intel Visual Fortran 10.0 through 11.1 with Microsoft Visual Studio 2003, 2005 or 2008.

Step 1 - are prerequisites met?

Open Microsoft Visual Studio from the Start menu. Select Help > About. Look for the following items:

In Visual Studio 2005 and 2008, make sure that it does not say "Express Edition". Visual Studio Express Edition is not supported for use with Intel Visual Fortran from within the Visual Studio development environment
If you are using a Standard, Professional or Team System Edition of Visual Studiom under Installed Products, look to see if "Microsoft Visual C++" is listed. If it is not, reinstall Visual Studio and make sure that the Visual C++ component is installed. If you are using the Microsoft Visual Studio 2005 Premier Partner Edition (included with Intel Visual Fortran 10.0, 10.1 and 11.0 - no edition name will be displayed), or Microsoft Visual Studio 2008 Shell (included with Intel Visual Fortran 11.1), Visual C++ is not required
Look under Installed Products to see if "Intel Visual Fortran Compiler Integration" is listed and make a note of the version number or "Package ID" displayed, if any.

Close Visual Studio

Step 2 - are the integration files present?

Check to see if the appropriate Intel folder is present. The paths given here are defaults and may vary on your system:

VS2003: C:\Program Files\Microsoft Visual Studio .NET 2003\Intel Fortran\VFPackages
VS2005: C:\Program Files\Microsoft Visual Studio 8\Intel Fortran\VFPackages
VS2008: C:\Program Files\Microsoft Visual Studio 9.0\Intel Fortran\VFPackages

Check to see if this folder contains six DLL files Windows may hide the file type for DLL files - the file names are VFAVwin.dll, VFFortSvc.dll, VFHieEditor.dll, VFProj.dll, VFProjConvert.dll, VFToolOpt.dll. If any of these files are not present, uninstall and reinstall Intel Visual Fortran.

Right click on VFProj.dll and select Properties, then click on the Version tab. Look at the "File Version" displayed. It will be in the form of 11.1.3464.2008. The first two numbers (11.1 here) indicate the compiler version. These must match that of the most recent version of the compiler installed. The last number (2008 here) indicates the Visual Studio version this DLL is for. If the compiler version does not match, uninstall Intel Visual Fortran, delete the entire "Intel Fortran" folder under the appropriate Microsoft Visual Studio folder, then reinstall Intel Fortran.

Step 3 - run the repair tool

If the above steps do not resolve the problem, download the appropriate ZIP file indicated below and run the executable file included within. Note: If you are running Windows Vista, Windows 7 or Windows Server 2008, run the program by right clicking it and selecting "Run as Administrator". In many cases, this will resolve the problem. If it does not, or if an error during registration of a DLL is noted, contact Intel Support for further options.

VS2003 Repair Tool
VS2005 Repair Tool
VS2008 Repair Tool

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

rc.exe not found-MS Visual Studio 2008 Shell

Mon, 10 Aug 2009 08:51:52 -0700

Reference Number :
DPD200138680

Version :
11.1.035
a related issue for Microsoft Visual Studio 2005, Premier Partner Edition can be found here

Operating System :
Windows XP, Windows Vista

Problem Description :
After performing an uninstall of the Intel Visual Fortran Compiler, subsequent attemps to build solutions using MS Visual Studio 2008 shell fail displaying the message 'rc.exe not found'.

There are several ways to reproduce this issue. One way is to install the compiler and VS 2008 shell from w_cprof_p_11.1.035. Next, install the compiler from w_cprof_p_11.1.038. Finally, uninstall version 11.1.035 of the compiler. Attempts to build solutions under VS 2008 shell now fail.

Resolution Status :
A problem report has been filed (see reference number). The workaround is to reinnstall the release with VS 2008 shell deselcting MKL, the documentation and IDE integration. On reinstall, do a "Repair" and then deselect,

all MKL components
Integration(s) in Microsoft Visual Studio
Integrated Documentation

This will restore the components accidentally deleted by the 11.1.035 uinstall without writing over the 11.1.038 integration.
This problem will be resolved in a future release of the Intel(R) Visual Fotran Compiler for Windows.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Undefined symbol _DftiCreateDescriptor_s_1d referenced - DFT change since MKL 10.1

Thu, 16 Jul 2009 22:28:17 -0700

DFT have change in latest version. In general, you can use them without problem. For who upgrade from previous version to new version, some latent problems may show up.

Problem 1: Undefined symbol '_DftiCreateDescriptor_s_1d' referenced in x.c

in MKL 10.1 release notes:
Improvements to the Discrete Fourier Transform Interface (DFTI)

- Addition of the DftiCopyDescriptor convenience function
- Reduction in the size of statically linked executables calling DFTI functions
- Support for DFTI_REAL_REAL storage (i.e., real and imaginary parts in separate arrays) in complex-to-complex transforms

In order to reduce the size of statically linked executable, we introduce specific functions in mkl_dfti.h
like DftiCreateDescriptor_s_1d, DftiCreateDescriptor_s_md for different dimensions DFT. The specific function is used by the preprocessor macro definition. Some DFT application in C/C++ may run into the compiler error
"Undefined symbol '_DftiCreateDescriptor_s_1d' referenced in x.c"

Resolution :
you can safely undefine it after inclusion of the Intel MKL FFT header file, as follows:
    # include "mkl_dfti.h"
    # undef DftiCreateDescriptor
or add compiler flag
    "-DDftiCreateDecriptor=DftiCreateDescriptor" into preprocessor definitions of your project

Problem 2: Program crashed when upgrade to MKL 10.1

Regarding the data layout in fortran Interface, take the code real_1d_ccs_double_ex6.f90 as sample
(DFT_VF_sample.zip is Intel Fortran project sample)
It is Fortran-interface, do Real to CCS packed 1D DFT. But the input and output data are from the column of two -dimension array. So the data storage layout need to be considered.

     Program REAL_1D_CCS_DOUBLE_EX6
      real(8) :: X_IN_2D (M_MAX,N_MAX)
      real(8) :: X_IN    (M_MAX*N_MAX)
      real(8) :: X_OUT_2D(M_MAX+2,N_MAX)
      real(8) :: X_OUT   ((M_MAX+2)*N_MAX)
      !      complex(8) :: X_OUT_C((M_MAX/2+1)*N_MAX)
      equivalence (X_IN, X_IN_2D)
      equivalence (X_OUT, X_OUT_2D)
    !      equivalence (X_OUT_C, X_OUT_2D)

    integer   strides_in(2)
      integer   dist_in
      integer   strides_out(2)
      integer   dist_out
      dist_in = M_MAX
      ! works with MKL Version 10.0.1 Product Build 072211.12 for 32-bit applications
      !$      dist_out = (M_MAX+2)/2

      !! works with MKL Version 10.1.0 Product Build 081809.14 for 32-bit applications and later
      dist_out = M_MAX+2
     Status = DftiCreateDescriptor( Desc_Handle, DFTI_DOUBLE, &DFTI_REAL, 1, n )
     Status = DftiCommitDescriptor( Desc_Handle )
     ! Status = DftiComputeForward( Desc_Handle, X_IN, X_OUT)
       Status = DftiComputeForward( Desc_Handle, X_IN, X_OUT_C)
        ....
X_OUT_C and dist_out = (M_MAX+2)/2 worked in previous version, but broken in latest version.

Resolution:
To set dist_out=M_MAX+2

The use of X_OUT_C and dist_out = (M_MAX+2)/2 in previous version works because the DftiCompute function in previous version reinterpret "the distance parameter" according to the X_OUT_C data type, which is corrected in latest version.

According to the code,
Status = DftiCreateDescriptor( Desc_Handle, DFTI_DOUBLE, &DFTI_REAL, 1, n )
Status = DftiCommitDescriptor( Desc_Handle )
It is a 1D real to CCS real transform and DftiComputeForward() will request two real array as input and output. And the value of dist_out shoud be the distance in real-type array, not complex-type array. So dist_out=M_MAX+2
is right value.

See more in MKL manual:
Once the descriptor is committed, the parameters of the transform, such as the type and number of transforms, strides and distances, the type and storage layout of the data, and so on, are "frozen" in the descriptor.   It should not be expected that DftiComputeForward would reinterpret the strides/distances.

Internal Compiler Error

Thu, 02 Jul 2009 10:24:50 -0700

Problem Description

A compilation fails with a message similar to one of the following:

example.c(22): internal error:

Please visit 'http://www.intel.com/software/products/support' for assistance.

[ Aborting due to internal error. ]

compilation aborted for example.c (code 1)

catastrophic error: **Internal compiler error: internal abort**

Please report this error along with the circumstances in which it occurred in a Software Problem Report.

Note: File and line given may not be explicit cause of this error.

compilation aborted for example.f90 (code 3)

Explanation

This message usually indicates a compiler defect.

Please report the problem to Intel through the Intel® Software Network Forums or Intel® Premier Support (support license and registration required). You will need to supply a test case along with a list of the compile options used and the exact compiler version that shows the problem. If you are not using a current compiler version, try the most recent version available to you as the error may have already been corrected.

Please note that this message is generic in nature and does not have a single cause nor solution. Providing a test case that reproduces the error is the only way to get a precise analysis of the problem.

In some, but not all, cases, you can work around the error by reducing the optimization level. You may find it helpful to try compiling with fewer switches to see if you can find one that, when removed, eliminates the error. It is also helpful to remove or comment out portions of the source file to see if you can isolate the line or lines that trigger the problem. The smaller the test case, the easier it will be for Intel to resolve the problem.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Intel Visual Fortran 11.1 and Visual Studio 2008 Shell Questions and Answers

Tue, 23 Jun 2009 10:12:55 -0700

Introduction : Installation Notes for Intel Visual Fortran Professional Edition 11.1 Related to Bundled Microsoft Visual Studio* 2008 Shell

Version : Intel Visual Fortran Professional Edition 11.1

Known Issues:

Fortran documentation not available from HELP menu in VS08 Shell

Intel Visual Fortran 11.1 and VS08 Shell Installation Questions and Answers :

Question: What is the Microsoft Visual Studio* 2008 Shell and Libraries? Do I need it? Do I want it?

Answer: The Microsoft Visual Studio* 2008 Shell and Libraries (VS08 Shell) is an integrated development environment (IDE) that is bundled with the Intel Visual Fortran Compiler Professional Edition 11.1 for users with Commercial or Academic licenses (all other licenses read the Q&A at the end of this page).
Do I need it, do I want it?: This Fortran-only development environment can be used by customers who do NOT have an existing prerequisite Microsoft development environment (see the Required and Optional Microsoft* Development Software article.) If you already own a supported Microsoft development environment you probably will not want or need VS08 Shell.

With the release of Intel Visual Fortran Professional Edition 11.1, VS08 Shell is provided as a replacement for the Microsoft Visual Studio 2005 Premier Partner Edition (VSPPE) packaged with versions 10.x and 11.0 of the Intel Visual Fortran Compiler. If you have VSPPE installed, read the question below:

Question: Before installing Intel Visual Fortran Professional Edition 11.1 I had a working installation of Microsoft Visual Studio* 2005 Premier Partner Edition (VSPPE). After installation of Intel Visual Fortran Professional Edition 11.1 I find that my VSPPE no longer works (Fortran compiler is not visible). Is this a bug?

Answer: The Commercial and Academic licensed versions of Intel Visual Fortran 11.1 come bundled with the Microsoft Visual Studio* 2008 Shell (VS08 Shell). This is intended to replace your older VSPPE environment. During installation of Intel Visual Fortran Pro 11.1, any VSPPE integrations are removed from the system prior to the installation of VS08 Shell. Instead of starting VSPPE, simply start Microsoft Visual Studio* 2008 Shell. If you wish to re-install the previous version integration into VSPPE, run the previous version's installer, select Modify and then enable only Visual Studio 2005 integration in the Component selection screen. Continue with the installation.

Question: Can I simply install the Intel Visual Fortran 11.1 compiler into my existing VSPPE installation?

Answer: No, Intel Visual Fortran 11.1 supports integration into VS08 Shell and/or integrations into FULL versions of Microsoft Visual Studio. Please read the 'Release Notes' document for Intel Visual Fortran for Windows Profession Edition 11.1 for details about supported development environments.

Question: Can VS08 Shell co-exist on a system with a full version of Microsoft Visual Studio* 2008?

Answer: No, only one integration into Visual Studio* 2008 can exist on a system. So you must choose if you want VS08 Shell or your own copy of Microsoft Visual Studio* 2008 (Standard or Pro). Because VS08 Shell has limited functionality, you will probably want to have Intel Visual Fortran 11.1 integrate into your existing Microsoft Visual Studio* 2008 (Standard, Professional or Team System Edition). This is the default behavior of the compiler installer: if any qualifying full version of Microsoft Visual Studio* is found, Intel Visual Fortran Pro 11.1 will simply integrate into that environment and not install the VS08 Shell. See the 'Release Notes' document for Intel Visual Fortran Pro 11.1 for an explanation of the limitations of VS08 Shell compared to the full version of Microsoft Visual Studio* 2008.

Question: I have a full vesion of Microsoft Visual Studio (or multiple versions of Visual Studio) installed on my system. After Intel Visual Fortran Pro 11.1 installation I now see the 11.1 compiler in my existing environment(s). However, I did not get an option to install VS2008 Shell and I do not see it installed on my system. Can I install VS08 Shell manually? Is there any reason I would not want to install VS08 Shell?

Answer: The Microsoft Visual Studio* 2008 Shell has limited functionality compared to a full version (Standard or Profession) of Microsoft Visual Studio* 2008. Please read the 'Release Notes' document that came with the Intel Visual Fortran Pro 11.1 compiler for a list of features that are not provided in the VS08 Shell. For this reason, you may wish to continue to use your existing Visual Studio rather than the Intel Visual Fortran Compiler Pro 11.1 provided VS08 Shell. If you do not already have Microsoft Visual Studio 2008 installed, you can install VS08 Shell manually. Assuming you downloaded and installed the "full" installer that includes VS08 Shell, open the folder C:\Program Files\Intel\Download\FortranCompilerPro11.1\installs\1033\w_cprof_vs2008 and run install2008shell.exe from that folder. After it completes, open Add or Remove Programs in Control Panel, select Intel Visual Fortran 11.1, select Change/Remove, then Modify. At the Component selection screen, make sure that Integrations into Microsoft Visual Studio is selected and click Next. Proceed with the installation.

Question: Now that I have VS08 Shell installed, can I install Intel C/C++ into my VS08 Shell environment so I can do mixed language programming?

Answer: No, the VS08 Shell provided with your Intel Visual Fortran Pro 11.1 will support Intel Visual Fortran ONLY . No other languages will integrate and work in this IDE.

Question: I do not see the Microsoft Visual Studio* 2008 Shell bundled with my Student licensed Intel Visual Fortran 11.1. Where is it, or how do I get it?

Answer: Student editions of Intel Visual Fortran 11.1 do not contain VS08 Shell. You must purchase a Commercial or Academic licensed Intel Visual Fortran 11.1 to obtain VS08 Shell.

Question: I do not see the Microsoft Visual Studio* 2008 Shell bundled with my evaluation version of Intel Visual Fortran 11.1. Where is it, or how do I get it?

Answer: Evaluation editions of Intel Visual Fortran 11.1 do not contain VS08 Shell. You must purchase a Commercial or Academic licensed Intel Visual Fortran 11.1 to obtain VS08 Shell. If you wish to evaluate Intel Visual Fortran 11.1 and do not own a version of Microsoft Visual Studio*, see the Required and Optional Microsoft* Development Software article.

Question: I do not see the Microsoft Visual Studio* 2008 Shell bundled with my 'Compiler Suite' product. Where is it, or how do I get it?

Answer: 'Compiler Suite' products do not contain VS08 Shell. This is because you are purchasing a C++ and Fortran compiler suite: VS08 Shell only supports Fortran and NOT C++. If you purchase a suite with both Fortran and C++ it is assumed that you have a need for mixed language programming and VS08 Shell does not fit this scenario. In this scenario you probably will want to separately purchase a full version of Microsoft Visual Studio* so that you can have support for mixed-language programming. You must purchase a Commercial or Academic licensed Intel Visual Fortran Pro 11.1 to obtain VS08 Shell. If you wish to evaluate Intel Visual Fortran 11.1 and do not own a version of Microsoft Visual Studio*, see the Required and Optional Microsoft* Development Software article.

Question: I don't see my question or answer here. Where can I get an answer?

Answer: Post a question on the Intel Visual Fortran User Forum, which is HERE.

IMSL Install Fails with Remote Activated License

Fri, 29 May 2009 08:59:39 -0700

Reference Number : DPD200136072

Version : 11.1

Operating System : Windows

Problem Description : If you install Intel Visual Fortran Compiler Professional Edition with IMSL* 11.1 and choose to activate the compiler license remotely (typically because the system you are installing on does not have Internet access), and then install the IMSL software, the IMSL install will not recognize the license that was activated from the compiler install.

Remote Activation is selected during install by entering a serial number, selecting "Choose alternative activation" and then, on the next screen, "Choose remote activation". You are presented with a code to be entered on a web page and submitted; you are then given an activation code to enter at the install screen. This process installs a license file on your system that is good for the installed version only - it does not authorize product updates. Entering a serial number for the product that includes IMSL, due to an error, installs a license that does not authorize installation of IMSL.

Resolution Status : This problem will be corrected in an update to version 11.1. Workarounds include:

Registering the serial number at the Intel Software Development Products Registration Center and copying the license file that is emailed to the system on which you wish to install IMSL. This license file can then be specified when you install the IMSL component. This has the advantage of installing a license that provides for software updates for the duration of your support term.
Repeating the remote activation sequence when installing IMSL.

If you have comments on this article, please enter them below. If you have a support question, please post it in our user forum.

Syntax error for array constructor with datatype keyword value

Mon, 18 May 2009 11:04:35 -0700

Reference Number : DPD200111543

Version : 11.0

Operating System : All

Problem Description : The compiler gives a syntax error for an array constructor of the form:

(/parameter-name/)

where parameter-name is a PARAMETER constant that has the same name as a datatype keyword (BYTE, INTEGER, REAL, COMPLEX, etc.) For example:

INTEGER, PARAMETER :: BYTE = 123
INTEGER IA(1)
IA = (/BYTE/)
END

When compiled, this gives an error such as:

example.f90(3): error #5082: Syntax error, found ')' when expecting one of: ( ...
IA = (/BYTE/)
------------^

Resolution Status : This problem is fixed in the January 2009 product update. A workaround is to use the Fortran 2003 array constructor syntax:

[parameter-name]

instead.

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]