I recently am dubbing a program where it comes acros a read error.

So the breakpoint occurs in a library routine.

The output pane gives a traceback where the READ error occurred, but

I am wondering why I cannot go to the routine and examine the contents of the variables in that routine.

The stack window does not allow me to go to the routine that has the READ statement.

Is there a way around this, other that having to insert print statements there?

Hello,

I am really new to coarray. I am trying a trying a simple example:

program ex
    print *, this_image(), num_images()
end program

I compile with ifort /Qcoarray ex.f90. Then, when I simply run ex.exe in the console, nothing happens, the programs just hangs. If, however, I run mpiexec -n 1 ex, then it runs, and it prints 4 lines.

If I set FOR_COARRAY_DEBUG_STARTUP=1, then, when I run ex.exe directly in the console, it prints Generated MPI command line is 'mpiexec.exe -localonly -n 4 ex ' before hanging.

So, I try to run mpiexec.exe -localonly -n 4 ex directly in the command line, and it hangs too. Without -localonly, it runs, and with -n 4, I get four times the line Generated MPI command line is 'mpiexec.exe -localonly -n 4 ex ', and 16 lines output from the program.

I wonder what I am doing wrong. If I interpret correctly, coarray is using MPI, but I should not type mpiexec to run the program, it will be called automatically. However, it seems mpiexec doesn't like the -localonly option.

In case it's important, I use IVF 2017.1 on Windows 7, both 64 bits.

Jean-Claude Arbaut

Hello,

I have a main program and two modules, where one module defines input used throughout the subroutines of the main program (call it commons) and the other one evaluates a function (call it mixture_mod). From the main program I call a subroutine in mixture_mod and pass some input. I would like that input to be "global" for the mixture_mod, because the subroutine uses another subroutine with the same input. The variables in two modules have the same names, and I believe that IMPLICIT NONE and PRIVATE should isolate the input variables in mixture_mod from the rest of the program. It seems not to be the case, as I receive the errors:

error #6279: A specification expression object must be a dummy argument, a COMMON block object, or an object accessible through host or use association   [NVR]    

error #6841: An automatic object must not appear in the specification part of a module.   [X]    

I am wondering  if there is a way to isolate variable names in  mixture_mod so that they do not clash with the same names used in the main program? A solution could be to rename the variables, but I am not sure this is sufficient as I would like mixture_mod to be able to stand along from the rest of the program. Or maybe this is not what causes the errors, but what then? 

Thank you in advance. The code is provided.

MODULE MIXTURE_MOD
    IMPLICIT NONE
    PRIVATE
    PUBLIC      :: getmixture
    INTEGER(4)  :: nvr,nfk,nx
    REAL(8)	:: x(nvr,nx),qw(nx),logphi(nx)
 CONTAINS

SUBROUTINE getmixture(nvr0,nx0,qx,qw0,logphi0,nfk0,th)
    INTEGER(4),INTENT(IN)            :: nvr0,nx0
    INTEGER(4),INTENT(OUT)           :: nfk0
    REAL(8),INTENT(IN)	             :: qx(nvr0,nx0),qw0(nx0),logphi0(nx0)
    REAL(8),ALLOCATABLE,INTENT(OUT)  :: th(:)
    REAL(8)	                     :: th0(6),fstar
    INTEGER(4)	                     :: k

nvr=nvr0; nx=nx0; x=qx; qw=qw0; logphi=logphi0;
nfk=1; k=6; th0=0d0;
CALL fcn(k,th0,fstar);
nfk0=nfk;
ALLOCATE(th(6)); th=th0;
END SUBROUTINE getmixture

SUBROUTINE fcn(npk,th_f,fd)
 IMPLICIT NONE
      INTEGER(4), INTENT(IN)   :: npk
      REAL(8), INTENT(IN)      :: th_f(npk)
      REAL(8), INTENT(OUT)     :: fd
!Uses specification part of the module as intermediate input
fd=1d0;
END SUBROUTINE fcn

END MODULE MIXTURE_MOD

MODULE commons
   IMPLICIT NONE
   SAVE
  	INTEGER(4)		:: nvr,nfk,nk,nx
	REAL(8),ALLOCATABLE	:: qw(:),x(:,:),logphi(:)
END MODULE commons

PROGRAM test
USE commons
USE MIXTURE_MOD
IMPLICIT NONE
	REAL(8),ALLOCATABLE	:: th1(:)

nvr=2; nk=5 ; nx=nk**nvr
ALLOCATE(qw(nx),x(nvr,nx),logphi(nx))
x=1d0; qw=1d0; logphi=1d0
CALL getmixture(nvr,nx,x,qw,logphi,nfk,th1)

END PROGRAM test

I have Intel Parallel Studio 2015 (via floating license) installed on my desktop, and recently purchased an IMSL add-on license. But the IMSL installation failed, with the error message of "the license file provided is invalid". 

Any thoughts of what might go wrong?

Hello all

I recently updated my compiler (see the attached About VS 2103.txt which contains all of the tools installed) and when I try to create a new project, I don't see any options for Intel Projects.  I checked the software update center, no new updates are available. 

Any clue as to why I don't see Intel options?

Ted

Hi guys,

I got a client who has just bought this and he says that he cant install on 32 bit machine and it's 64 bit only. Is this true as he has been told this from Intel support.

Thanks,

Mark

I use Quickwin a lot, but not usually with customizations to the menu bar. When I have tried this, I have been bamboozled by its interaction with child windows. Specifically, sometimes, a "rogue" window "Graphic1" is created, which persists throughout the program, as I am not able to delete it programmatically.

Recently through LOTS of trial & error study, I have learned how to control the problem, so I wanted to (a) share it, (b) find out if this is the normal behavior, and (c) suggest better documentation.

As explained in the documentation, child windows are invisible until they are written to, or if SETWINDOWCONFIG is called. What should be added to this list is customizing the menu bar using DELETEMENUQQ, APPENDMENUQQ, etc. Apparently, these calls attempt to display the current child window. If there is none, then it will create and display a "rogue" child window "for it's own use"?

Apparently, as I have found in various example programs I have found, these menu calls are commonly made *after* the creation of a child window using an OPEN call, for example OPEN (unit=1, file='USER). In this case, the menuqq calls execute with no problem: They don't actually write anything to the open window,  although if nothing has yet been written, the window will be invisible, the menu call will make it visible, and it can then be deleted if the user wants.

But to me, it is generally logical to customize the menu bar before doing anything else with child windows, including any OPEN statements. This is when I run into trouble--the menuqq calls create this rogue window that is visible and persists, and resists efforts to CLOSE it. The solution is to code something like this:

PROGRAM MenuDemo
: various initializations
! Assume menu manipulations are the first thing to me done.
OPEN (0, file = 'USER')
​lreturn = DELETEMENUQQ (menuno, itemno)
​: Additional menuqq calls
​CLOSE (0)
​! Program continues

I wish I had discovered this years ago--would have saved me hours of frustration and coping.

Is this behavior well known or considered standard, or acceptable? I think the documentation should describe this undesirable side effect of the menuqq functions, along with some discussion of how to control it.

Hi,

I am new using intel fortran to write subroutine for abaqus.

In my subroutine, I need to read some data (this data is pre-generated by matlab) and then pass to other subroutines for calculation. The data I am currently reading is text file, they are quite big and it seems that ABAQUS takes quite some time just reading this file. So I am thinking to use binary files instead.

I have to admit that I am never work with binary file before, a quick check online indicates that I can use .mat file or netcdf format for binary files. But it seems that for both format, we need extra library. But since what I wrote is just a subroutine and the main function is by abaqus, so my questions would be:

1) can I read .mat or .nc file in the abaqus subroutine?

2) if not, do you have any recommendation that how should I read these data in my subroutine to speed up my simulation? 

Thanks!

I just had a computer "GO SOUTH" and I have the new one up and running.

But the Fortran XE 2017 I downloaded wont run. I installed it using my previous license file,

and it went thru all  62 pieces, but I get an unusable result.

So which Fortran should I get, and how do I get it ?

BTW why does a CR take me to the top of the page ?

Don't they test this stuff ?

Hello,

i got an error with the XE17.1 compiler. The following code produces two different crashes in line 35 (coming from 68), dependend on the type of "vec" in "T_VECTOR". The code worked with the XE16.X compilers.

module M_T_VECTOR
  implicit none

  type :: T_VECTOR
!forrtl: severe (408): fort: (7): Attempt to use pointer ASSIGN_SOURCE when it is not associated with a target
    real :: vec(1:3) = [0.0,0.0,0.0]

!forrtl: severe (157): Program Exception - access violation
!    doubleprecision :: vec(1:3) = [0.0,0.0,0.0]
  contains

    procedure :: assignTo
    generic :: assignment(=) => assignTo
    procedure ::add
    generic :: operator(+) => add

  end type T_VECTOR

  type, extends(T_VECTOR) :: T_VECTOR_EXT

    type(T_VECTOR),  allocatable :: disp(:)
    class(T_VECTOR_EXT), pointer :: pt_a    => null()
    class(T_VECTOR_EXT), pointer :: pt_b(:) => null()

  end type T_VECTOR_EXT

!--------------------------------------------------------
contains

  elemental subroutine assignTo(assign_target, assign_source)
    class(T_VECTOR), intent(inout) :: assign_target
    class(T_VECTOR), intent(in   ) :: assign_source

! Exception thrown here
    assign_target%vec = assign_source%vec

  end subroutine

  elemental function add(lhs, rhs) result(ergebnis)
    class(T_VECTOR), intent(in   ) :: lhs, rhs
    type(T_VECTOR)                 :: ergebnis

    ergebnis%vec = lhs%vec + rhs%vec
  end function

end module M_T_VECTOR

!========================================================

program main
  use M_T_VECTOR
  implicit none

  type(T_VECTOR_EXT), target :: a,b(2)

  a%pt_b => b
  a%pt_a => a

  allocate(a%disp(2))
  allocate(b(1)%disp(2))
  allocate(b(2)%disp(2))

  !This works
  a%pt_a%disp(1) = a%pt_a%disp(1) + a%pt_b(1)%disp(1)
  a%pt_a%disp(2) = a%pt_a%disp(2) + a%pt_b(1)%disp(2)

  !This crashes
  a%pt_a%disp(:) = a%pt_a%disp(:) + a%pt_b(1)%disp(:)

end program

Greetings

Wolf

Hi,

I'm  rookie in using Fortran. I'm using IVF 2013 and VS 2005 to compile and test a console application written by fortran. The code is intended to transform the residues and poles of a rational function into the form of numerator and denominator. Following is my code:

SUBROUTINE res2num(res,poles,k,norder,den,num)
!*********************************************************
! Convert a rational function from pole-residue form to numerator-denominator form
! k is the constant term
!*********************************************************
    IMPLICIT NONE
    COMPLEX(KIND=8),DIMENSION(:),INTENT(IN)::res,poles
    COMPLEX(KIND=8),INTENT(IN)::k
    INTEGER,INTENT(IN)::norder
    COMPLEX(KIND=8)::num(norder+1),den(norder+1),numtmp(norder)
    COMPLEX(KIND=8)::tmp(2)
    INTEGER::i,j,cntSkip,sizenumtmp

    den=1d0
    num=0d0
    tmp=0d0
    ! Get the denominator
    DO i=1,norder
        tmp(1)=1
        tmp(2)=-poles(i)
        CALL conv(tmp,den(norder+2-i:norder+1),2,i,den(norder+1-i:norder+1))
    ENDDO
    ! Get the numerator
    DO i=1,norder
        numtmp=1d0
        cntSkip=0d0
        DO j=1,norder
            sizenumtmp=SIZE(numtmp,1)
            IF(j/=i) THEN
              tmp(1)=1
              tmp(2)=-poles(j)
              CALL conv(tmp,numtmp(norder+1-j+cntSkip:norder),2,j-cntSkip,numtmp(norder-j+cntSkip:norder))
            ELSE
                cntSkip=1
             ENDIF
        ENDDO
        num(2:norder+1)=res(i)*numtmp(1:norder)+num(2:norder+1)
    ENDDO
    num(2:norder+1)=num(2:norder+1)+den(2:norder+1)*k
    num(1)=k*den(1)
        RETURN
ENDSUBROUTINE res2num

And the subroutine conv computes the convolution between two 1D vectors vecA and vecB, and outputs another 1D vector whose dimension equals to SIZE(vecA，1）+SIZE(vecB，1）-1. This conv subroutine has been tested OK if it is directly called within the main program.

However, when debugging the subroutine res2num, there is always a run time error, saying the stack was corrupted. I've tried to diagnose which line of the code cause the error and it turns out to be the line

CALL conv(tmp,numtmp(norder+1-j+cntSkip:norder),2,j-cntSkip,numtmp(norder-j+cntSkip:norder))

As the subroutine conv is already tested OK, I'm quite confused why there is such an error

p.s. I've already increase the stack reserve size to 999999999 in the project property windows.

any suggestions?

This is a simple test for ifort.

test.90:

integer a,b,c
a = 1
b = 2
call sub(a,b,c)
write(*,*)'c=',c
stop
end

sub.f90:

subroutine sub(a,b,c)
integer a,b,c
c=a+b
return
end

The makefile is:

lib     = sub.lib
exe     = test.exe

$(lib):
    ifort /c sub.f90
        lib /out:$(lib) sub.obj

$(exe):
        ifort test.f90 sub.lib

clean:
 -del *.exe *.obj

I first make the library with the command

make sub.lib

Then I try to make the exe with the command

make test.exe

This gives an error on linking - LNK1104: Cannot open file ifconsol.lib.

However, if I give the command

ifort test.f90 sub.lib

at the command prompt, the program is made without error.

Why is the makefile causing this error?

Thank you.

Hello,

I am using Intel Parallel Studio XE 2015 Update 7 Composer Edition for Windows to compile Fortran files with  C-Files. I addition I have installed Visual Studio 2013 and Visual Studio 2015.

I have a solution opened in VS2015 which is a mixed Fortran/C-solution to generate a static lib file. The platform toolset of the C project is set to VS2013, but when I compile the Fortran project the /Qvc14 switch is set. How can I change to /Qvc12 to use VS2013 instead?

When I link that lib to other object files I get the error "LINK : fatal error LNK1104: cannot open file 'legacy_stdio_definitions.lib'". Using google I found out, that this happens when compiling with VS2015.

For testing purpose I added the fortran files to the C project and used the custom build tool setting to compile the fortran files. When doing so, I can link the resulting lib (combined Fortran/C-sources) successfully to my other projects. So I guess the Qvc switch is responsible for this error.

I read that I can change that setting by reinstalling the compiler. Is there another option to fix this without a reinstallation or is there an option in the properties window of the Fortran project which I didn't recognize yet?

Thank you very much!

Hi,

in the beginning of the year I purchased a license renewal. the order summary minus the serial is given below. This was the product recommended by the registrationcenter websitre for license renewal. It took me until the weekend to actual update to the latest version and found that the license is not valid. I contact support (premier.intel.com) and got the following response:

"Hi Sir,

The date 22 Feb 2017 is  the support expiration date (shown in the attached snapshot).
You can submit tickets to ask questions, report issues and get helps in the support period.
But your license expiration date is 21 Feb 2016.
After the license expires, you cannot use the tool any longer.
Please apply a new academic license for using Parallel Studio XE again.

Best regards,
Soflen"

Is the support engineer correct that the fee of $649 does not include use of current software? In this case I spent $649 for asking the single question as to why my license is not working. I must say this would be absolutely appalling and not the way one treats a customer of 10 years.

Advice and clarifications greatly appreciated.

Thanks,

Haje

Order Summary:
Product: Intel® Parallel Studio XE Composer Edition for
Fortran Windows* with Rogue Wave* IMSL* Support
Services Renewal
Serial Number 1: XXXX-XXXXXX
SKU: PRI999WSGM01ZZZ
Vendor: Lifeboat
Version: 2016
License Type: Named-user
Number of Seats: 1
Quantity: 1
Support Code: commercial
FulfillmentType: ESD
Support Period End: 2017-02-22

I looked at that registration page with my current license, and all I could find was the XE 2017 stuff, and XE 2013 Build 6.

Are we to understand that those other releases are forbidden to us ?

What is wrong with them ?

Anyway, I went ahead and installed XE 2013 because there are several issues with 2017.

Better that, than nothing - - - -

Hi, all,

I have a subroutine in abaqus for which I want it to just read some data file and then pass is to the other subroutine 'DLOAD'. The data I am reading now is a array with the size of 169*12001. If I make the data file formated as ASCII, then it's working fine. Now I want to speed up for the reading, so I think of binary files. Then there is this error message like 'aborted with system error code 1073741571.' And it seems that it's related to memory overflow in ABAQUS. I tried to downsize the data file and it works. So I was trying to using multiple subroutines to read small binary files seperately. But the error come again when I call several subroutines.

I have tried to allocate memory for the array I read inside the subroutine, then it’s working, but the allocated memory is only existing inside of the subroutine and can’t pass data to other subroutine.

I also read the abaqus manual ‘http://50.16.225.63/v6.14/books/sub/default.htm?startat=ch02s01abu23.html’ But I don’t quite follow the explaining there.

I understand this is more a problem in ABAQUS instead of the compilier, but I put up the thread here hoping someone who have experiences with ABAQUS can also take a look and give comments.

Thanks!

Jungao

Hi,

I often get the error message attached when I try to run an exe file that is calling a dll module in the debug mode. The exe file is located in the specified directory and sometimes it works when I keep cleaning the solution and building. I have to restart VS every time I build the project in order to overcome the issue. Help will be appreciated.

DownloadDownload

I have a project setup as a static library in Visual Studio 2015.  After I finish each module, I do a test compile to catch any errors and in particular if I forgot to add the necessary USE statements.   I just finished a large module which contains numerous calls to subroutines in other modules (already completed and compiled).  The module compiled with only warnings about missing functions.  When I added the appropriate USE statements for the functions, the module compiled without any errors or warnings despite missing all the USE statements containing the subroutine definitions.   I did a test compile with all USE statements removed in case there was some hidden propagation of the needed subroutines.  The module compiled with only messages about the functions.

Can someone help explain why the compiler is not complaining about the missing subroutine definitions?  And why it is complaining about the missing function definitions?  By the way, before compiling the latest module, I make sure all the other modules have been compiled.

Here are my compiler options:

/nologo /debug:full /Od /stand:f08 /warn:declarations /warn:unused /warn:interfaces /module:"x64\Debug\\" /object:"x64\Debug\\" /Fd"x64\Debug\vc140.pdb" /list:"x64\Debug\static_library.lst" /traceback /check:bounds /check:stack /libs:dll /threads /dbglibs /c

Thanks….

I get the following error when I press F12 when in debug mode, if I press 'continue' I can carry on.

I hadn't noticed this before but I loaded an old version of the software and it still happens - maybe I haven't been pressing F12 when in debug mode.

Reading other posts, they hadn't been pressing F12.

Should I not be using F12 - or is there a bug in my software. If there is, can you suggest how I can track it down.

Thanks

---------------     

'Grade.exe': Loaded 'C:\DavidG\Grade\GradeSource\Grade\Debug\Grade.exe', Symbols loaded.
'Grade.exe': Loaded 'C:\Windows\System32\ntdll.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\kernel32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\KernelBase.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\user32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\win32u.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\version.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\gdi32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\msvcrt.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\gdi32full.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\advapi32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\sechost.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\rpcrt4.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\comdlg32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\combase.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\ucrtbase.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\bcryptprimitives.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\SHCore.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\shlwapi.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\shell32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.0_none_88fef4c26039fb25\comctl32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\cfgmgr32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\windows.storage.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\powrprof.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\kernel.appcore.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\profapi.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\ole32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\imagehlp.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\winspool.drv', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\wsock32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\ws2_32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\bcrypt.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\oleaut32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\msvcp_win.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\imm32.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\uxtheme.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\msctf.dll', Cannot find or open the PDB file
'Grade.exe': Loaded 'C:\Windows\System32\dwmapi.dll', Cannot find or open the PDB file
The thread 'Win32 Thread' (0x2244) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xc84) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x718) has exited with code 0 (0x0).
'Grade.exe': Loaded 'C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.0_none_74bc87d3d22d9abe\comctl32.dll', Cannot find or open the PDB file

Windows has triggered a breakpoint in Grade.exe.

This may be due to a corruption of the heap, which indicates a bug in Grade.exe or any of the DLLs it has loaded.

This may also be due to the user pressing F12 while Grade.exe has focus.

The output window may have more diagnostic information.
The thread 'Win32 Thread' (0x1528) has exited with code 0 (0x0).
The program '[7060] Grade.exe: Native' has exited with code 0 (0x0).