Microsoft Windows* 8.x

intel visual fortran running error


I got problems running an existing code. When I try to run the code created by CVF. the intel visual fortran give me the error "the system can not find file specified". I am not sure if I put the code and the file needed in the right directory. Can anybody tell me how to put the code and file needed in the right directory?  

Also, when the intel visual fortran run the code, it gives me error "compilation aborted". Can any one tell me how to solve this problem?

Windows 8* Store vs Desktop App Development

When developing apps for Windows 8 and Intel devices, you have a unique opportunity and decision regarding which type of Windows 8 app you would like to develop. The following article helps define and point to resources to help you decide which type of app development is for you.

  • Desenvolvedores
  • Desenvolvedores Intel AppUp®
  • Microsoft Windows* 8.x
  • Windows*
  • Principiante
  • Windows 8* Store
  • Desktop App Development
  • Área de trabalho do Microsoft Windows* 8
  • Estilo de interface do Microsoft Windows* 8
  • ifort: command line warning #10122:


    I use ifort 11.1.072 with the following comman line:

    ifort -D__EFL -DNOSTDCALL -DARGTRAIL -O3 -DPCWIN64_SYS -DPCWINX64_SYS -DPCWINNT_SYS -DCADOE_ANSYS -Qfpp -nbs -4Yportlib -4Ya /c /Fo.\ /DFORTRAN /MD /W0 /object:"..\objects"\ /module:"..\modules"\ /include:%I

    and I get the following warning for every source file:

    ifort: command line warning #10122: overriding '/object.\' with '/object..\objects\'

    I want to get rid of the warning messages.

    Please can anyone explain to me, what is wrong in the ifort commant.



    overhead when using subroutine - how to use inline

    Hi all,

    I have tried to test if there was an overhead in using a subroutine compared to not doing so. It was my impression that for small functions etc. the compiler would automatically inline the functions having the meaning that there was no overhead in using a subroutine call or function. However I have made a test example that shows otherwise (or perhaps I am not using the right compiler settings). The test is this (see also attached source):

    do i=1,nLoop

      call MySubroutine(Var1,var2,...Var20)

    end do


    do i=1,nLoop

    Var1 = Var1 + 1.5

    Problem calling a dummy callback from Fortran

    I have a problem calling a dummy callback from Fortran.

    We have a C++ program which calls Fortran code, EQCONTOUR.
    It passes a function pointer (FCALL) when calling this subroutine.
    The purpose is to provide a callback function that the Fortran can call back in the C++ world to echo progress, etc.
    This all works fine and here is the code:

    EQCONTOUR uses this module:

    Designer Tools for Windows Desktop Applications

    Download PDF

    As technology has matured, our approach for design has evolved from command line to graphical interfaces. In the document Design for Desktop Touch and the Ultrabook™, we covered how the new touch input requires us to be aware of and design software for these new usage patterns. What does the designer need to consider when designing for the Ultrabook desktop?

  • Desenvolvedores
  • Microsoft Windows* 8.x
  • Windows*
  • Intermediário
  • Área de trabalho do Microsoft Windows* 8
  • Interfaces de toque
  • Design e experiência do usuário
  • Architecture Pattern: Compute On Demand

    There are so many examples of applications using pre-processing strategy that it is trivial. For example using a webcam we often find the device driver doing some software adjustments and corrections such as white balancing. Too often we find devices using software features. Other examples would be in a pipeline and User Interfaces. When it comes to UI we already learned to fill the list when the user clicks the drop-down, so only when the user really wants to use the list we will "pay" for the data.

    Fortran DLL's call stack in XE2013 debugger weird compared to XE2011 -- integration problem?

    Hi folks-

    Win7 x64, XE 2013 is being used to debug into a Fortran DLL, where the main program is written using Delphi 2009.  The main app manually exports some Delphi routines by passing their addresses to the Fortran DLL, which imports them using Cray pointers and interface blocks.  I have all of the calling conventions worked out, and Delphi routines can call the Fortran DLL routines, and vice versa.  After a lot of help from this forum, I even got the parameter passing correct...  I'm very confident that this technique works.

    Assine o Microsoft Windows* 8.x