Quantcast
Channel: Intel® Software - Intel® Visual Fortran Compiler for Windows*
Viewing all 5691 articles
Browse latest View live

Difficulty integrating VS and PSXE

$
0
0

Hello,

I am trying to compile a .f90 file provided by the National Renewable Energy Lab for their program OpenFAST.  They supply the .f90 file and a CMake file, and instruct the user to run the CMake file.

I have Visual Studio 2017 and the other day I downloaded Parallel Studio XE 2018, the 30 day trial.  I have been unable to get CMake to recognize the Fortran compiler.

VS has the Desktop Development C++ package, and PSXE is integrated with VS.  If I type ifort in to any command window I get a response, so it's there.  I found this article about troubleshooting Fortran integration: https://software.intel.com/en-us/articles/troubleshooting-fortran-integr....  At the end of step 2 it says to look at the file version of the integration DLLs.  My DLL versions don't quite fit the style of that example, but the last numbers are 15.  How did I get integration DLLs for VS 2015?  I only have 2017 installed. 

I read on another Intel article (I can't find it again right now) that if PSXE does not recognize the version of Visual Studio then it will install the integration for the 2015 shell.  Under the release notes for PSXE 2018, https://software.intel.com/en-us/articles/intel-visual-fortran-compiler-..., it says that the trial version does not come with the 2015 shell version though.

Is my problem because PSXE is in the 30 day trial?  If not, how do I  get the correct integration DLLs?  I've spent 6 days trying to compile this one file.  I'm not a programmer, I'm just trying to compile the controller to use this NREL program to simulate wind turbines.

Thank you.


Where can I find IMSL with my IVF?

$
0
0

Hi there,

I bought "Parallel Studio XE Composer Fortran Win NmdComm ESD", and it is supposed to be bundled with IMSL. But, I cannot find where is IMSL after I installed it.

Thanks

Liu

Set Path

$
0
0

Have a DLL project associated to a console application in a specified solution.

Initially the DLL was created using files that were added from a location.

These files were removed and the same files that are the source for the console application are the ones for the DLL portion of the project.

Upon compilation, the DLL and the associated object files are stored in a location that is "divorced" from the main solution itself.

The question is....how to update the path for the DLL portion of the project so it can be a part of the same solution?

As well, what does ERROR 48 indicate?

These are two (2) different problems although they may be related?

Thank you.

18.01 compiled routine "missing ordinal 747"

$
0
0

Colleagues.

We install our commercial code on a 'naked' machine for testing and dependency checking. The code is compiled as an x64 console application with compiler release 18.01 and runs without incident on the development machine within VS 2017. We have installed (says here) the Fortran redistributable using: ww_ifort_redist_intel64_2018.1.156.msi -- the installer ran without incident. But attempting to run our code on the 'naked' machine generates this error: 

The ordinal 747 could not be located in the dynamic link library C:\Program Files (x86)\Acuity Brands\Visual Lighting 2017\Program\Engine\Eng_ShapeMesh.exe

1) What is 'ordinal 747'?

2) Why is the message calling our .exe a dll?  Our code is a x64 console application.

This problem only arose when we moved to release 18 of the compiler. No such problems when complied with 16.04.

 

MSVS Version

$
0
0

I'm about to get a replacement machine setup.

Is MSVS2017 sufficiently stable to get that on my machine, or should I stick with MSVS2015?

Thanks

ERROR 49 BAD DLL CALLING CONVENTION FROM VBA

$
0
0

Code behind excel that has been successfully used before to call a DLL yields a new error, Error 49.  Have tried several variations including PTRsafe as well as removing the "alias".  Any ideas out there?

C++ and Fortran mixed code link error

$
0
0

Hello,

I’m using Visual Studio 2017 Community with the Intel Fortran compiler. With my current configuration the “C_calls_Fortran" example contained in the “MixedLanguage" package from Intel builds and runs on Win32 but does not fully build on x64. I get a LNK1104 error, cannot open file 'kernel32.lib’ with x64. 

 

I implemented the configuration setup at: https://software.intel.com/en-us/articles/configuring-visual-studio-for-mixed-language-applications

for x64.

 

I’ve looked at and tried a lot of examples in the forum to no avail. In Project Properties, settings in VC++ Directories are:

 

Include Directories: $(IFORT_COMPILER18)\compiler\include\intel64;$(IncludePath)

Library Directories: $(IFORT_COMPILER18)\compiler\lib\intel64;$(LibraryPath)

 

there are more than a few versions of kernel32.lib loaded on my computer and I’m guessing that I’m referencing the wrong one. The value of IncludePath is:

 

C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_20189.1.156\windows\\compiler\include;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.12.25827\include;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\T

 

Ideas for fixing this problem?

 

Thanks.

Using Intel Trace analyzer with windows and VS2015

$
0
0

Hi,

I'm trying to use Intel Trace analyzer with windows and VS2015 on my CFD code.

In my code, I have many F90 files but different modules and subroutines. Also, I'm linking with other libraries such as PETSc.

I tried to add "/trace" in the additional commands in VS2015 GUI and compile. However, after running my code, there is no *.stf generated.

I then tried to do it in cygwin, on another smaller code, by adding -trace to the compiling and building. Similarly, no *.stf is generated.

I also tried to compile and build directory in the command prompt:

mpiifort /c /MT /Z7 /fpp /Ic:\wtay\Lib\petsc-3.8.3_win64_impi_vs2015_debug\include /trace   /o ex2f.obj ex2f.F

mpiifort /MT /trace /o ex2f.exe ex2f.obj /INCREMENTAL:NO /NOLOGO /qnoipo /LIBPATH:"C:\wtay\Lib\petsc-3.8.3_win64_impi_vs2015_debug\lib" Gdi32.lib User32.lib Advapi32.lib Kernel32.lib Ws2_32.lib impi.lib impid.lib impicxx.lib impicxxd.lib libpetsc.lib libflapack.lib libfblas.lib kernel32.lib

Now I can get the *.stf file.

But is there some way to do it in VS2015? As mentioned, I have many F90 files and I hope I do not have to use the command line.

Thanks.


The INTERFACE/CONTAINS stack is full, Superclass and Subclass pointing to each other

$
0
0

Hey 

I have a circular dependencie. Is there any way to solve this in fortran?

MODULE mElement
	USE mProject
	IMPLICIT NONE
	
	PRIVATE
	PUBLIC :: tElement
	
	TYPE :: tElement
		INTEGER(4) :: element_property = 1234
		TYPE(tProject), POINTER	:: project
	END TYPE tElement
END MODULE mElement

	
MODULE mProject
	USE mElement
	
	TYPE :: tProject
		TYPE(tElement), ALLOCATABLE :: elements(:)
	END TYPE tProject
	
END MODULE mProject
	
	
PROGRAM TEST
	USE mElement
	USE mProject
	IMPLICIT NONE

	TYPE(tProject) :: project
END PROGRAM TEST

I have Superclass which is containing Subclass Objects. The Subclass should point back to its Superclass

Error when writing to a file from a child window

$
0
0

I am migrating a QW CVF application to QW IVF. The program has a main window with a menu. So  when selecting a menu item, an accompanying child window will be opened. The program can perform several calculations and the results are written on the screen (UNIT 13) and in addition the results are dumped to a text file (UNIT 7) for documentation purposes. However, unlike to CVF, the program does not accept a second unit.

If the child window ( 13) is opened first, the program fails to write data to the text file, unit 7 and vice versa. Please take a look at the attachment for more details.

Can anyone give me a tip ?

 

AttachmentSize
Downloadapplication/pdfError writing to file.pdf119.88 KB

BACKSPACE issue with different Intel Compiler version

$
0
0

Hi all,
I notice a difference between two different version of the same Fortran77  code compiled with 2011 and 2017 Intel Compiler.

The code is quite simple:

  • it opens an ASCII file and read it until a specific line, containing an integer number, N
  • the data from the next N lines are stored into an array
  • now - with the backspace command - we return to the position where data were stored and overwrite data with new values (elaborated somewhere else)

I can't post the full code here, but I prepare a simplified example below.

          open(2,file=filename,status='old')
c
		  read(2,*) N
		  do ii=1,N
		     read(2,*)  X(ii),Y(ii),Z(ii),T(ii)
		  enddo
c
		  do ii=1,N
			backspace(2)
		  enddo
c
		  do ii=1,N
			write(2,*) X(ii),Y(ii),Z(ii),T2(ii)
		  enddo

With a version of the code compiled with Intel 2011 compiler, the output is good, while if I compile with 2017 version, backspace does not work, and data are not overwritten, but stored "under" old data.

Sorry for my English, I hope that someone can help me.

Lorenzo

Install order for mutiple Visual Studio and Intel Compiler

$
0
0

I maintain extensions for python that must accommodate python 2.7+ in Windows and that utilize Intel Fortran (f2py). This means I need at least command line support of VS 2008, 2012 and 2017. I regularly use the command prompts from the Intel start menu as the environment for running f2py.

My machine recently got wiped clean and I need to reinstall everything. I remember order was critical and doing it wrong could even mess up the machine. I know I need to install the Visual Studio in chronological order. What I don't know is the minimum intel compilers that I need to install to cover 2008 - 2017. I'm hoping the most recent one plus some 2013 vintage will cover it nicely. 

Also, can someone tell me whether I should "shuffle" the Visual Studio and Intel installs like this:

VS 2008, VS2012, Intel "2013" (or whatever answers my first question), VS2017, Intel 2018

or

VS 2008, Intel "2013", VS2012, , VS2017, Intel 2018

or should I do all the Microsoft and then all the Intel:

VS 2008, VS2012, VS2017 then Intel "2013", Intel 2018

Which, if any, of these will work? Which will preserve integrated Fortran support in the GUI? I have read about the trick of backing up and replacing the Fortran integration folder.

 

 

integrating intel fortran compiler into VS

$
0
0

I have installed VS2017 and downloaded trial version of Intel Parallel Studio XE 2018. But, after trying to open the existing project, it reports that .vfproj is incompatible. I checked on the web site and seems there are some problems with integration of  FORTRAN in VS2018. Would be thankful if somebody could help me to clarify this problem

how to use pardiso in f90 program

$
0
0

What is the right way to "use" or "include" mkl_pardiso in an f90 program?
use mkl_pardiso generates a compile about not being to find the file in the include directory, but it can find blas95 and lapack95 without any trouble.

DLL INPUT FILES

$
0
0

Appear to have noticed that there is a difference in the location that an excel called DLL wants any utilized data (.dat) files based upon where the DLL itself is stored.  For example, when the DLL is stored in C:\Windows\System the files appear to be sought in C:\Users\Owner\Documents.  When the DLL is stored in SYSWOW it looks like the .DAT files can be in the same folder as the spreadsheet.  Is it understood how this works?  What are the associated rules around this?


Real type issue

$
0
0
I have a problem I have not encountered before that I remember.  mzaMax is determined from an element of vector, but when I try and use it in the DISLIN GRAF routine - the routine wants a real, so I get a compile error of incorrect type. 

DISLIN is not perfect but it is fast.  

Any help appreciated. 

INTEGER, PARAMETER :: dp = selected_real_kind(15, 307)

    integer :: counter
    REAL (KIND=dp) Eig(ndf,ndf), vector(ndf), mza(ndf), mzaMax
    REAL counterMZA


    call getX(eig,ndf)

    call setEigen(ndf, eig, sda, 1, vector, counter, mza, mzaMax, counterMZA)

    CDEV = 'xwin'    CALL METAFL(CDEV)
    CALL SETPAG('DA4L')

    FPI=PI/180.
    STEP=360./(N-1)

    DO K=1,N
        XRAY(K)=(K-1)*STEP
        X=XRAY(K)*FPI
        Y1RAY(K)=0.1
        Y2RAY(K)=COS(X)
    END DO

    CALL DISINI()
    CALL PAGERA()
    CALL HWFONT()
    CALL AXSPOS(450,1800)
    CALL AXSLEN(2200,1200)

    CALL NAME('X-axis','X')
    CALL NAME('Y-axis','Y')

    CALL LABDIG(-1,'X')
    CALL TICKS(10,'XY')

    CALL TITLIN('Eigenvector Plot ',1)
    CALL TITLIN(SDA(1),3)

    CALL GRAF(0.,counterMZA + 2.0 ,0.,1.0,-mzaMax,mzaMax,-mzaMax,mzaMax/4.0)

 

Real*4 and C_FLOAT

$
0
0

Hi,

I am working on integration of C program with Fortran subroutines - using C/Fortran interoperability (ISO_C_BINDING). When I pass single precision array from C to Fortran subroutine can I be ALWAYS sure that C_FLOAT is the same as REAL*4. So in other words inside Fortran procedure I want to use values of passed array (via pointer) and do not want to copy elements from C_FLOAT array to REAL*4 array (then conversion is - as I assume - automatic between these two) ? 

Best, 

Adam 

 

question about dodesol statistics

$
0
0

Do calls to dodesol return any information about the number of steps and function calls?  Perhaps in the ipar array?

question about visual studio

$
0
0

I added a .txt file to a vfproj project, and all hell broke loose.

After that visual studio would announce an "exception" when opening the solution containing this vfproj.  So I deleted the .txt file from the project, but VS still would throw an exception saying something about "an extension" was likely the problem.  The solution contains 12 projects.  11 of the projects seem to be behaving normally, but one of the projects would not behave in VS, meaning it properties could not be edited, and its source code files would open in "vanilla" mode and not in "fortran" mode (strangely, it's not the one I added the .txt file to).  If I close the solution, and just open the vfproj for the misbehaving project, it opens without any trouble, and behaves ok.  So I restarted VS, opened the sln, and deleted that vfproj from the sln, and then added it back again (all from within VS).  That seems to have solved the problem, i.e. no more exceptions.

Does anyone know what happened here?  What is the right way to add a .txt file to a project?  I would like to put project notes in the file.

The exception message said to launch VS with a /log command line switch, and look in ActivityLog.xlm for more info.  When I did that, there was one error message.  Here it is in case anyone knows what it means.

262 ERROR System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. at Microsoft.VisualStudio.VFProject.VFFile.get_SourceFileFormat() at Intel.Fortran.IFLangService.IFClassifier.OriginalSourceFileFormat() at Intel.Fortran.IFLangService.IFClassifier..ctor(IFClassifierProvider provider, ITextBuffer buffer) at Intel.Fortran.IFLangService.IFClassifierProvider.GetClassifier(ITextBuffer buffer) at Microsoft.VisualStudio.Text.Classification.Implementation.ClassifierTaggerProvider.<>c__DisplayClass1`1.<CreateTagger>b__0(IClassifierProvider provider) at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InvokeMatchingFactories[TExtensionInstance,TExtensionFactory,TMetadataView](IEnumerable`1 lazyFactories, Func`2 getter, IContentType dataContentType, Object errorSource)   Editor or Editor Extension 

 

Run EXE in another system without any FORTRAN support, extra DLLs support & Microsoft Visual Studio

$
0
0

I am using Intel Visual Fortran Compiler 15 with Visual Studio 13.

Suppose I make a simple program to add two numbers. When I use command line to compile, create object (obj), link and create exe, using the commands :-

ifort add.f90

ifort -o add add.obj 

The exe created by this method will run in any other system (running Windows) irrespective of the support of Fortran, Visual Studio, extra DLLs in it.

NOW !!!

When I use the Visual Studio to compile, build and even release than the exe created by this method which I find in some

C:\Users\VIVEK\Documents\Visual Studio 2013\Projects\Console1\Debugor 

C:\Users\VIVEK\Documents\Visual Studio 2013\Projects\Console1\Release

directory cannot run on independently run on any system (like it did in command line case). The other system reports for some error regarding DLLs. HERE I NEED HELP. I want to create the 'independent' exe from Visual Studio just like the command line did. I searched a lot in different forums and throughout the web but didn't found the exact steps that could help me. I know some dll linking or something is missing, such as dependencies. I am just a BEGINNINER in Visual Studio and it's settings. So can someone please help me with the step by step procedure. Please be detailed.

Thank You

PS:- I've also noted the difference in the size of the two exe. Eg. The exe created by the command line will be roughly near 100-120 KB (which I believe is the reason for it's independent nature). However, the exe created using the Visual Studio is somehwhat 20-30 KB.

 

Viewing all 5691 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>