Microsoft Windows* (XP, Vista, 7)

Constant File Parsing

Visual Studio seems to have started going crazy parsing my source files.  Everytime I press any key, I see the message at the bottom of the dialog that says "Parse file <filename>".  The constant delay from doing this is an big annoyance.  How do I turn this off?  In Options -> Fortran -> Advanced, I have everything set to False, except for "Disable Database", which I set to True.  It doesn't seem to help.  I'm using VS 2010, with the 2015 version of the compiler (initial release).

Find Windows* Threading Errors with Intel® Inspector XE

What threading errors in Windows can Inspector XE find?

 

Windows Threading Errors

Memory Error Analysis Type Configuration Setting Descriptions

The following table describes the purpose, usefulness, and cost (low, medium, high, or proportional in terms of time and resources) for each analysis type configuration setting. (The settings are listed in alphabetical order.)

  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • Windows*
  • Intel Inspector XE
  • threading
  • UNFORMATTED, ACCESS = SEQUENTIAL

    Hi guys,

    I've got following situation:

    - there is a code where I open and close a file with form='UNFORMATTED', access='SEQUENTIAL' 
    - the file is open several times with position='APPEND'

    The settings of the project include:
    - [COMPATIBILITY] use power station I/O format = YES
    - [DATA] use bytes as RECL = YES

    PROBLEM
    When trying to READ the data the results based on data are not correct. I've noticed that there is comma mark placed on file CLOSE.

    an interesting and serious topic

    Hello there:

             I have found an interesting  appearance which I can not explain. Okey, let's go.

             I apply "micsmc" to surveiling the offload running state of MIC. The critical code like this:

    #pragma offload target(mic:0) inout(XXXX) in (XXXX)
    {
    #pragma omp parallel for schedule (dynamic)
    for( int i = 0; i < num_cluster; i++) // num_cluster from 60 to 300,concentrated on 90~150
    {
      do something....
    }
    
    }

             And then set the environment variables :

    export OMP_NUM_THREADS=X
    export KMP_AFFINITY=compact

    Passing allocatable array to a subroutine

    I'm trying to pass an allocatable array, which is already allocated, to a subroutine. something like this:

    real(8), dimension(:,:), allocatable :: A
    
    allocate (A (6,6))
    
    call subroutine mysub(A)
    
    
    
    subroutine mysub(B)
    real (8), dimension (:,:) :: B
    
    write (*,*) B(1,1)
    
    

    This causes segmentation fault when mysub is accessing B. I have had the same approach to pass the array to a function and it worked fine. I wonder what's going wrong here. 

    Thanks,

    Alireza

    Find Windows* Memory Errors with Intel® Inspector XE

    What memory errors in Windows* can Inspector XE find?

     

    Windows Memory Errors

    Memory Error Analysis Type Configuration Setting Descriptions

    The following table describes the purpose, usefulness, and cost (low, medium, high, or proportional in terms of time and resources) for each analysis type configuration setting. (The settings are listed in alphabetical order.)

     

    Setting

    Purpose, Usefulness, and Cost

  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 8.x
  • Windows*
  • Intel® Inspector
  • threading
  • Subscribe to Microsoft Windows* (XP, Vista, 7)