Fortran

Cross-thread Stack Access

Hi All,

I'm running an OpenMP application (minimal example) :
  !$OMP PARALLEL DO

     DO KR=1,100

            Array_Out(KR) = Array_Input(KR)

    ENDDO 

  !$OMP END PARALLEL DO

 
I verified that I do not have data race (I get the same results with only one thread), however when running the application in the Inspector XE 2013 - I get a massage that I have cross-thread stack accesses. 

How can I prevent this behavior, and what is the practical effect if not on the results ?

Thanks in advance for your replies,

Using Intel® VTune™ Amplifier XE to Tune Software on the 5th generation Intel® Core™ processor family

Download this guide (see Article Attachments, below) to learn how to identify performance issues on software running on the 5th generation Intel® Core™ processor family (based on Intel® Microarchitecture Codename Broadwell). The guide explains the General Exploration Analysis viewpoint available in Intel® VTune™ Amplifier XE. It also walks through some of the most common performance issues that the VTune Amplifier XE interface highlights, what each issue means, and some suggested ways to fix them.

  • 开发人员
  • 教授
  • 学生
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • C#
  • C/C++
  • Fortran
  • Intel VTune Amplifier
  • app performance tools
  • application optimization
  • 开发工具
  • 优化
  • 并行计算
  • 线程
  • Debugging internal Fortran subroutine

    Hello,

    I have a Fortran subroutine that has internal subroutines and functions which it calls. The program runs, but once I step into an internal subroutine, debugging variables define in principal usbroutine is impossible. It is as if it does not inherit the debug information from the enclosing subroutine. All the variables are undefined in the debugger.

    Does anyone know how to get around this problem ?

    Visual studio version : 2012 update 4

    Open Source Downloads

    This article makes available third-party libraries, executables and sources that were used in the creation of Intel® Software Development Products or are required for operation of those. Intel provides this software pursuant to their applicable licenses. [Intel® Graphics Technology, Intel® Composer XE, Intel® C++ Composer XE, Intel® Application Debugger, Intel® Many Integrated Core Architecture Debugger & Intel® JTAG Debugger]
  • 英特尔 AppUp® 开发人员
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • C/C++
  • Fortran
  • 英特尔® C++ 编译器
  • Intel® Fortran Compiler
  • Intel® Debugger
  • Intel® JTAG Debugger
  • Eclipse
  • EPL
  • third-party
  • Intel(R) Software Development Products
  • Intel® Graphics Technology
  • Intel® Composer XE
  • Intel® C++ Composer XE
  • Intel® Application Debugger
  • Intel® Many Integrated Core Architecture Debugger & Intel® JTAG Debugger
  • 图形
  • 英特尔® 凌动™ 处理器
  • 开源
  • Fortran Runtime Library (forrtl) error numbers and iostat values

    Hi,
    I am working on improving error handling in my codes, and have ran into some questions:

    1) When reading a file, I want to check “iostat” values to see whether EOF is reached (IVF seems to set "iostat=-1" for EOF condition).

    Is there some named/parameterised value that can be used instead of hardcoding "-1"?

    I’d like something similar to "FOR$IOS_ENDDURREA" (forrtl=24), but for iostat values instead.

    And some follow on questions - would appreciate some general guidance:

    How to get a LIB project to link with an EXE project.

    I have a VS solution which contains two vfproj's.  One for a main program and one for a LIB.  I'm getting unresolved externals because the LIB doesn't seem to be getting linked with the EXE.  What is the proper way to set this up?  I'm using VS 2010.  With an old version of vs with cvf I vaguely recall typing the LIB's name into a field somewhere in project settings.  Is it still done that way today?

    lost installation in hard drive failure - now what?

    I owned a license to Intel Fortran, and had it on my machine.  I suffered a catastrophic hard drive failure (actually, two in a row), and the replacement drive no longer has the installation.

    I've been wandering around completely lost on the Intel site trying to figure out what to do.  The support seems deliberately designed to be impossible to contact for help.  I have the emails with the original product serial number and SKU, but I see nothing I can do with it.

    订阅 Fortran