Quantcast
Channel: Fortran
Viewing all 3108 articles
Browse latest View live

Referencing conditional logic

$
0
0

I have a .f90 file with dozens of subroutines, each of which require:

#ifdef _WINDOWS

#ifdef BITS64
  use apm_mod_Win_x64
#else
  use apm_mod_Win_x86
#endif

#else

#ifdef BITS64
  use apm_mod_Linux_x64
#else
  use apm_mod_Linux_x86
#endif

#endif

 

Is there a way to define this logic once and then just refer to it in each subroutine?

 

 


Using !$omp declare simd in an elemental subroutine

$
0
0

Quite recently (in May), I decided to update some of my codebase to use OpenMP 4.0 and, in particular, try out the "!$omp declare simd" directive. After a few teething troubles documented in a question I asked here, I got it working well and it has been running smoothly ever since. As it's such a short subroutine, I'll reproduce it here for convenience:

elemental subroutine Calculate_Sines(normal_x, normal_y, normal_z, &
                                     rzero_x, rzero_y, rzero_z,    &
                                     es_x, es_y, es_z, sin_theta)

!$omp declare simd(Calculate_Sines) uniform(normal_x, normal_y, normal_z)
    real(kind(1d0)), intent(in) :: normal_x, normal_y, normal_z
    real(kind(1d0)), intent(in) :: rzero_x, rzero_y, rzero_z
    real(kind(1d0)), intent(out) :: es_x, es_y, es_z, sin_theta

    es_x = normal_z * rzero_y - normal_y * rzero_z
    es_y = normal_x * rzero_z - normal_z * rzero_x
    es_z = normal_y * rzero_x - normal_x * rzero_y

    sin_theta = sqrt( es_x**2 + es_y**2 + es_z**2 )

end subroutine Calculate_Sines

However, I've just installed Parallel Studio XE 16.0 and everything has come to a juddering halt. The same piece of code now fails to compile, with the error message:

error #8807: An OpenMP* directive may not appear in a PURE procedure.

I assume that an elemental subroutine is pure by implication. My basic syntax isn't at all original, as it very closely follows an example given in the Intel documentation here, so I can't really figure out what I should do. Is the example in the documentation, which dates from May 2014 no longer valid? Or am I just doing something really dumb?

Is there any option in the intel fortran compiler (ifort) to compile and run the executable automatically after compiling?

$
0
0

I know that it is possible to compile in IVF from CMD by using the ifort command. However, that command only compiles and does not run the executable upon finishing compiling. The .exe needs to be run sequentially by hand.

Is there any automatic option in the ifort driver to compile and run the .exe automatically?

Thanks in advance.

Finalizer: only executed on scallar allocatable object.

$
0
0

In just want to confirm if this is the expected behavior of a finalizer.

In the code below,

module tes_final_mod
implicit none
type :: my_final
   integer :: n
   contains
      final :: destroy
end type my_final
contains
   subroutine destroy(self)
   type(my_final) :: self
   write(*,*), 'Destroy executed!'
   end subroutine destroy
end module tes_final_mod
!=============================
program tes_finalizer
use tes_final_mod
implicit none
type(my_final), allocatable :: a(:), b(:)
type(my_final), allocatable :: c
!
allocate(a(10))
a%n= 1
deallocate(a)
print*, 'a deallocated'
allocate(a(10))
a%n= 3
allocate(b(20))
b(1:10)= a
call move_alloc(b, a)
print*, 'b deallocated'
allocate(c)
c%n= 2
deallocate(c)
print*, 'c deallocated'
call call_final
contains
   subroutine call_final
   type(my_final) :: aa
   print*, 'SUB: Will finalize when returned.'
   return
   end subroutine call_final
end program tes_finalizer

I have the following result, when compiled with ifort Version 15.0.3.187 Build 20150407:

 a deallocated
 b deallocated
 Destroy executed!
 c deallocated
 SUB: Will finalize when returned.
 Destroy executed!

That is, the finalizer only runs when SCALAR allocatable objects are deallocated (object c in the main and aa in the subroutine).  Allocatable arrays are not finalized either by directly killing then with a deallocate (array a, first time) or by the move_alloc (array b).

Is this the expected behavior?

Even stranger, when the very same program is compiled with gfortran, the results are almost the same, with the exception of the last call on the finalizer, when the subroutine is exited.  With gfortran the return statement did not cause the finalizer to run.

Error:#11025 and #10014 in linux

$
0
0

My system is fedora 19 , the version is :

Linux version 3.14.27-100.fc19.x86_64 (mockbuild@bkernel02.phx2.fedoraproject.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) ) #1 SMP Wed Dec 17 19:36:34 UTC 2014

The ifort is parallel_studio_xe2016 for students, when inpit ''ifort --version'' in the terminal,there is :

ifort (IFORT) 16.0.0 20150815
Copyright (C) 1985-2015 Intel Corporation.  All rights reserved.

 

When compile a file with 'ifort 't.f95'(could be compiled with g95),there is :

ipo: error #11025: Linker command line is badly formed
ifort: error #10014: problem during multi-file optimization compilation (code 1)

If input 'ifot',there is :

ifort: command line error: no files specified; for help type "ifort -help"

Then I try to use 't.f90',input 'ifort t.f90 -o a.e',there is :

fortcom: Severe: No such file or directory

... file is 'daalvars.csh*'
compilation aborted for t.f90 (code 1).

That's all information I get.

Thank you for your help!

 

system crash when running dss on MKL_dss_indefinite

$
0
0

Hey there,

my dss implementation freezes the whole system, probably due running out of memory, when switching from positive_definite to indefinite.

The matrix provided to dss is 4x4, so not a big problem, but it is negative definite.

The module implementing the solver is:

include "mkl_dss.f90"
Module ModMKLSolver
  use Data_Kind
  use ModEquation
  use ModLogfile
  Implicit none
  Type MKLSolver
    Type(Equation) :: TSEq
  contains
    Procedure, Pass, Public :: Solve => SubSetPEVDSS
  End type MKLSolver
  Private :: SubSetPEVDSS
contains
  Subroutine SubSetPEVDSS(this,ISSubStat)
    use MKL_DSS
    Implicit None
    Class(MKLSolver), Target, Intent(InOut) :: this
    Integer(Iks), Intent(InOut) :: ISSubStat
    Integer(Ikxl) :: c1, c2
    TYPE(MKL_DSS_HANDLE) :: handle
    Integer(Ikxl) :: ISError
    Integer(Ikl) :: opt, a, ISSize
    Integer(Ikl), Allocatable, Dimension(:) :: IVPermu
    ISSize=this%TSEq%TSLHS%ISDim
    Allocate(&&IVPermu(ISSize),&&stat=ISSubStat)
    If(ISSubStat==0) Then
      IVPermu=0
      this%TSEq%RVsol=0._rkdbl
      ISSubStat=dss_create(handle, MKL_DSS_MSG_LVL_WARNING&&+MKL_DSS_TERM_LVL_ERROR)
      If(ISSubStat==0) Then
        ISSubStat=dss_define_structure(handle=handle,&&opt=MKL_DSS_SYMMETRIC,&&rowIndex=this%TSEq%TSLhs%IVRowPos,&&nRows=ISSize,&&RCols=ISSize,&&columns=this%TSEq%TSLhs%IVColPos,&&nNonZeros=size(this%TSEq%TSLhs%RVCoeff))
      End If
      If(ISSubStat==0) Then
        ISSubStat=dss_reorder(handle=handle, opt=MKL_DSS_GET_ORDER, perm&&=IVPermu)
      end If
      If(ISSubStat==0) Then
        ISSubStat=dss_factor(handle=handle,&
          !&opt=MKL_DSS_POSITIVE_DEFINITE,&&opt=MKL_DSS_INDEFINITE,&&RValues=this%TSEq%TSLhs%RVCoeff)
      End If
      If(ISSubStat==0) Then
        ISSubStat=dss_solve(handle=handle,&&opt=0,&&RRhsValues=this%TSEq%RVRHS,&&nRhs=1,&&RSolValues=this%TSEq%RVSol)
      End If
    End If
  end Subroutine SubSetPEVDSS
end Module ModMKLSolver

The implementation works with setting "positive_definite" and matrices which abide by that rule.

Compiler: ifort 15, System: ubuntu 14.04

Any suggestions??

Thanks

Karl

OpenMPI stoped working

$
0
0

Hallo!

I have the Intel Parallel Studio XE Composer installed and additionally I build OpenMPI with the intel compiler (based on: https://software.intel.com/en-us/articles/performance-tools-for-software-developers-building-open-mpi-with-the-intel-compilers). I aolso sourced all path which I need to get it working on linux. It worked perfectly till frieday but today it just stopped working and i got this error message:

/opt/OpenMPI-intel/include/mpif-config.h(33): error #6236: A specification statement cannot appear in the executable section.
      integer OMPI_MAJOR_VERSION, OMPI_MINOR_VERSION
------^
/opt/OpenMPI-intel/include/mpif-config.h(34): error #6236: A specification statement cannot appear in the executable section.
      integer OMPI_RELEASE_VERSION
------^
/opt/OpenMPI-intel/include/mpif-config.h(35): error #6236: A specification statement cannot appear in the executable section.
      parameter (OMPI_MAJOR_VERSION=1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(36): error #6236: A specification statement cannot appear in the executable section.
      parameter (OMPI_MINOR_VERSION=10)
------^
/opt/OpenMPI-intel/include/mpif-config.h(37): error #6236: A specification statement cannot appear in the executable section.
      parameter (OMPI_RELEASE_VERSION=0)
------^
/opt/OpenMPI-intel/include/mpif-config.h(41): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_OFFSET_KIND, MPI_ADDRESS_KIND, MPI_INTEGER_KIND
------^
/opt/OpenMPI-intel/include/mpif-config.h(42): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_COUNT_KIND
------^
/opt/OpenMPI-intel/include/mpif-config.h(43): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_INTEGER_KIND=4)
------^
/opt/OpenMPI-intel/include/mpif-config.h(44): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_ADDRESS_KIND=8)
------^
/opt/OpenMPI-intel/include/mpif-config.h(45): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_OFFSET_KIND=8)
------^
/opt/OpenMPI-intel/include/mpif-config.h(46): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_COUNT_KIND=8)
------^
/opt/OpenMPI-intel/include/mpif-config.h(50): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_STATUS_SIZE
------^
/opt/OpenMPI-intel/include/mpif-config.h(51): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_STATUS_SIZE=6)
------^
/opt/OpenMPI-intel/include/mpif-config.h(55): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_PROCESSOR_NAME
------^
/opt/OpenMPI-intel/include/mpif-config.h(56): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_ERROR_STRING
------^
/opt/OpenMPI-intel/include/mpif-config.h(57): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_OBJECT_NAME
------^
/opt/OpenMPI-intel/include/mpif-config.h(58): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_LIBRARY_VERSION_STRING
------^
/opt/OpenMPI-intel/include/mpif-config.h(59): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_INFO_KEY
------^
/opt/OpenMPI-intel/include/mpif-config.h(60): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_INFO_VAL
------^
/opt/OpenMPI-intel/include/mpif-config.h(61): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_PORT_NAME
------^
/opt/OpenMPI-intel/include/mpif-config.h(62): error #6236: A specification statement cannot appear in the executable section.
      integer MPI_MAX_DATAREP_STRING
------^
/opt/OpenMPI-intel/include/mpif-config.h(63): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_PROCESSOR_NAME=256-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(64): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_ERROR_STRING=256-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(65): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_OBJECT_NAME=64-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(66): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_LIBRARY_VERSION_STRING=256-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(67): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_INFO_KEY=36-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(68): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_INFO_VAL=256-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(69): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_PORT_NAME=1024-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(70): error #6236: A specification statement cannot appear in the executable section.
      parameter (MPI_MAX_DATAREP_STRING=128-1)
------^
/opt/OpenMPI-intel/include/mpif-config.h(75): error #6236: A specification statement cannot appear in the executable section.
      logical MPI_SUBARRAYS_SUPPORTED
------^
dnspipe.f(39474): catastrophic error: Too many errors, exiting
compilation aborted for dnspipe.f (code 1)
make: *** [dnspipe.o] Error 1

 

Getting Started with Intel® VTune™ Amplifier 2016 for Systems (Linux* Host)

$
0
0

Intel® VTune™ Amplifier for Systems Performance Profiler with Intel® Energy Profiler helps you speed up and optimize execution of your code on Linux* embedded platforms, Android* or Windows* systems providing the following types of analysis:

  • Performance analysis: Find serial and parallel code bottlenecks, analyze algorithm choices, GPU engines usage, and understand where and how your application can benefit from available hardware resources.

  • Intel Energy Profiler analysis: Analyze power events and identify those that waste energy.

VTune Amplifier for Systems is available as part of the Intel System Studio.

Select Your Host System to Get Started

Prerequisites

  • For remote analysis, set up your target Linux* | Android* system.

  • For hardware event-based sampling analysis, make sure you have the sampling driver installed. Note that for Linux targets the sampling driver detects the kernel update and automatically attempts to rebuild and load the driver at the boot time. If, for some reasons, the sampling driver cannot be installed, the VTune Amplifier automatically enables driverless Perf*-based collection providing limited event-based sampling analysis options.

  • For Intel Energy Profiler analysis, make sure to have the appropriate drivers installed for your target Linux | Android system.

For system requirements, see the product Release Notes.

Get Started with Performance Analysis

Step 1: Start the VTune Amplifier

  1. Set up the environment variables:

    • csh/tcsh users: source <install_dir>/amplxe-vars.csh

    • bash users: source <install_dir>/amplxe-vars.sh

    By default, the <install_dir> is:

    • For root users: /opt/intel/system_studio_<version>/vtune_amplifier_for_systems

    • For non-root users: $HOME/intel/system_studio_<version>/vtune_amplifier_for_systems

  2. Launch the VTune Amplifier:

    • For standalone GUI interface, run the amplxe-gui command.

    • For command line interface, run the amplxe-cl command.

Step 2: Set Up the Analysis Target

  1. Build your target application in the Release mode with all optimizations enabled.

  2. Create a VTune Amplifier project:
    1. Click the menu button in the right corner and go to New > Project... .

    2. Specify the project name and location in the Create Project dialog box.

  3. In the Analysis Target tab, select a target system from the left pane and select an analysis target type from the right pane.

  4. Configure your target: application location, parameters and search directories (if required).

Step 3: Configure Analysis

  1. Switch to the Analysis Type tab.

  2. From the left pane, select an analysis type applicable to your platform and configure analysis options in the right pane.

  3. Click the Start button on the right to launch the analysis.

Step 4: View and Analyze Performance Data

When data collection completes, the VTune Amplifier opens the result in the default viewpoint, which is a preset configuration of windows for an analysis result. You may switch between different viewpoints to analyze the data from different perspectives using different sets of performance metrics.

Start your analysis with the Summary window to get an overview of the application performance and then switch to other windows to explore the performance deeper at the granularity of function, source line and so on.

Get Started with Energy Analysis

Depending on your target system, the VTune Amplifier uses different collectors for energy and power analysis.

Android* Targets:

  1. Connect to the target Android system via an adb shell command.
  2. Load device drivers and install the Intel SoC Watch collector on the target Android system.

  3. Run the data collection on the target. For example:

    >./socwatch -t 60 -f cpu-cstate -m -r vtune -o ./results/test

    where: -t 60 specifies collection duration in seconds, -f cpu-cstate enables C-state and wakeups analysis, -m specifies the maximum level of detail, and -r vtune creates a *.pwr file that can be imported into VTune Amplifier. The analysis result *.pwr file will be located in the ./results/test directory.

  4. Copy the result file (*.pwr) to the host.

  5. Open/create a VTune Amplifier project and click the Import toolbar button to import the energy analysis result file into the project.

  6. Explore the Platform Power Analysis viewpoint to view the collected data.

Linux* Targets:

  1. Load device drivers and install the Intel SoC Watch collector on the target Linux system.

  2. Run the data collection on the target. For example:

    >./socwatch -t 60 -f cpu-cstate -m -r vtune -o ./results/test

    where: -t 60 specifies collection duration in seconds, -f cpu-cstate enables C-state and wakeups analysis, -m specifies the maximum level of detail, and -r vtune creates a *.pwr file that can be imported into VTune Amplifier. The analysis result *.pwr file will be located in the ./results/test directory.

  3. Copy the result file (*.pwr) to the host.

  4. Open/create a VTune Amplifier project and click the Import toolbar button to import the energy analysis result file into the project.

  5. Explore the Platform Power Analysis viewpoint to view the collected data.

Documentation and Resources

Document

Description

Intel VTune Amplifier Tutorials

Tutorials show you how to configure remote collection with the VTune Amplifier and use basic product features. VTune Amplifier tutorials guide a new user through basic walkthrough operations with a short sample. The tutorials provide an excellent foundation before you read the VTune Amplifier help.

To view available VTune Amplifier for Systems tutorials, open the index.htm file, which is installed at <install-dir>/documentation/<locale>/tutorials.

Sample code is typically installed to <install-dir>/samples/<locale>/<programming_language>.

Release Notes

The Release Notes contain the most up-to-date information about the product, including a product description, technical support, and known limitations and issues.

This document also contains system requirements for installing the product. Before installation, the Release Notes document is located at the root level (same level as the installation script/executable) of the installation download package.

The Release Notes document is installed at: <install-dir>/documentation/<locale>/release_notes_amplifier_for_systems_linux.pdf

Installation Guide

The Installation Guide contains basic installation instructions for VTune Amplifier and post-installation configuration instructions for the various drivers and collectors.

The latest Installation Guide can be found on the Intel Developer Zone website.

Intel VTune Amplifier Help

The help is the primary documentation for the VTune Amplifier. To view VTune Amplifier help, do the following:

  • From the product interface: Choose Intel VTune Amplifier 2016 for Systems Help from the Help menu, or click the Help button on the toolbar.
  • Outside the product interface: Open the index.htm file, which is installed at <install-dir>/documentation/<locale>/help.

Intel SoC Watch User's Guide (Android* | Linux* target system)

This document provides detailed instructions on using the Intel Energy Profiler command line data collector, Intel SoC Watch, for power and energy analysis on target systems. For information on viewing and interpreting energy analysis data, see Intel VTune Amplifier Help > Energy Analysis User's Guide chapter.

SEP User's Guide

This document provides instructions on using the VTune Amplifier sampling collector (SEP) targeted for hardware event-based sampling analysis on resource-restricted systems.

Intel Processor Event Reference

This help provides reference information for Intel processor events used by the VTune Amplifier for hardware event-based sampling analysis. To access the Event Reference, choose Intel Processor Event Reference from the Help menu, or click the Help icon on the toolbar.

Command line help

You can access general help for VTune Amplifier command line interface by entering the following command line:

  • amplxe-cl -help for help on basic action options

  • amplxe-cl -help <action-option> for help on a particular action option and its knobs

Web Resources

Legal Information

Intel, VTune and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.

* Other names and brands may be claimed as the property of others.

Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Copyright © 2013-2015, Intel Corporation. All rights reserved.


Getting Started with Intel® VTune™ Amplifier 2016 for Systems (Windows* Host)

$
0
0

Intel® VTune™ Amplifier for Systems Performance Profiler with Intel® Energy Profiler helps you speed up and optimize execution of your code on Linux* embedded platforms, Android* or Windows* systems providing the following types of analysis:

  • Performance analysis: Find serial and parallel code bottlenecks, analyze algorithm choices, GPU engines usage, and understand where and how your application can benefit from available hardware resources.

  • Intel Energy Profiler analysis: Analyze power events and identify those that waste energy.

VTune Amplifier for Systems is available as part of the Intel System Studio.

Select Your Host System to Get Started

Click for Getting Started steps on Linux* host

Click for Getting Started steps on OS X* host

Prerequisites

  • For remote performance analysis, set up your target Linux* | Android* system.

  • For hardware event-based sampling analysis, make sure you have the sampling driver installed.

    Note that for Linux targets the sampling driver detects the kernel update and automatically attempts to rebuild and load the driver at the boot time. If, for some reasons, the sampling driver cannot be installed, the VTune Amplifier automatically enables driverless Perf*-based collection providing limited event-based sampling analysis options.

  • For Intel Energy Profiler analysis, make sure to have the appropriate drivers installed for your target system.

For system requirements, see the product Release Notes.

Get Started with Performance Analysis

Step 1: Start the VTune Amplifier

  1. Set up the environment variables with the amplxe-vars batch file. For example, if you installed the VTune Amplifier using the default directory, type: C:[Program Files]\IntelSWTools\system_studio_2016.0.<package_num>\VTune Amplifier for Systems\amplxe-vars.bat. Batch file displays the product name and the build number.

  2. Launch the VTune Amplifier:
    • For standalone GUI interface, run the amplxe-gui command.
    • For command line interface, run the amplxe-cl command.

Step 2: Set Up the Analysis Target

  1. Build your target application in the Release mode with all optimizations enabled.

  2. Create a VTune Amplifier project:
    1. Click the menu button in the right corner and go to New > Project... .

    2. Specify the project name and location in the Create Project dialog box.

  3. In the Analysis Target tab, select a target system from the left pane and select an analysis target type from the right pane.

  4. Configure your target: application location, parameters and search directories (if required).

Step 3: Configure Analysis

  1. Switch to the Analysis Type tab.

  2. From the left pane, select an analysis type applicable to your platform and configure analysis options in the right pane.

  3. Click the Start button on the right to launch the analysis.

Step 4: View and Analyze Performance Data

When data collection completes, the VTune Amplifier opens the result in the default viewpoint, which is a preset configuration of windows for an analysis result. You may switch between different viewpoints to analyze the data from different perspectives using different sets of performance metrics.

Start your analysis with the Summary window to get an overview of the application performance and then switch to other windows to explore the performance deeper at the granularity of function, source line and so on.

Get Started with Energy Analysis

Depending on your target system, the VTune Amplifier uses different collectors for energy and power analysis.

Android* Targets:

  1. Connect to the target Android system via an adb shell command.
  2. Load device drivers and install the Intel SoC Watch collector on the target Android system.

  3. Run the data collection on the target. For example:

    >./socwatch -t 60 -f cpu-cstate -m -r vtune -o ./results/test

    where: -t 60 specifies collection duration in seconds, -f cpu-cstate enables C-state and wakeups analysis, -m specifies the maximum level of detail, and -r vtune creates a *.pwr file that can be imported into VTune Amplifier. The analysis result *.pwr file will be located in the ./results/test directory.

  4. Copy the result file (*.pwr) to the host using an adb pull command on the host: adb pull <*.pwr_file>

  5. Open/create a VTune Amplifier project and click the Import toolbar button to import the energy analysis result file into the project.

  6. Explore the Platform Power Analysis viewpoint to view the collected data.

Windows* Targets:

  1. Install the Intel SoC Watch collector on the Windows system. VTune Amplifier provides two instances of the Intel SoC Watch collector for Windows targets:

    • For host-based collection, the Intel SoC Watch collector is installed by default with the Intel System Studio and available from the [Program Files]\IntelSWTools\system_studio_for_windows_<version>\VTune Amplifier <version> for Systems\target\windows_socwatch directory.

    • For remote Windows targets, install the Intel SoC Watch collector.

  2. Run the data collection on the target. For example:

    > socwatch -t 60 -f cpu-cstates -m -r sww -o results/test

    where: -t 60 specifies collection duration in seconds, -f cpu-cstates requests C-state and wakeup analysis, -m specifies the maximum level of detail, and -r sww creates a *.sww1 file that can be imported into VTune Amplifier. The output files will be named test and be located in the results directory.

  3. Copy the result file (*.sww1) to the host.

  4. Open/create a VTune Amplifier project and click the Import toolbar button to import the energy analysis result file into the project.

  5. Explore the Platform Power Analysis viewpoint to view the collected data.

Linux* Targets:

  1. Load device drivers and install the Intel SoC Watch collector on the target Linux system.

  2. Run the data collection on the target. For example:

    >./socwatch -t 60 -f cpu-cstate -m -r vtune -o ./results/test

    where: -t 60 specifies collection duration in seconds, -f cpu-cstate enables C-state and wakeups analysis, -m specifies the maximum level of detail, and -r vtune creates a *.pwr file that can be imported into VTune Amplifier. The analysis result *.pwr file will be located in the ./results/test directory.

  3. Copy the result file (*.pwr) to the host.

  4. Open/create a VTune Amplifier project and click the Import toolbar button to import the energy analysis result file into the project.

  5. Explore the Platform Power Analysis viewpoint to view the collected data.

Documentation and Resources

Note

If you have problems viewing VTune Amplifier documentation on the Microsoft Windows Server* 2012 system, adjusting a security setting for the Microsoft Internet Explorer* browser usually corrects the problem. From Tools > Internet Options > Security, add about:internet to the list of trusted sites. Optionally, you can remove about:internet from the list of trusted sites after you are finished viewing the documentation.

Document

Description

Intel VTune Amplifier Tutorials

Tutorials show you how to configure remote collection with the VTune Amplifier and use basic product features. VTune Amplifier tutorials guide a new user through basic walkthrough operations with a short sample. The tutorials provide an excellent foundation before you read the VTune Amplifier help.

The default installation location for the VTune Amplifier tutorials is <install-dir>\documentation\<locale>\tutorials\index.htm.

To open the VTune Amplifier tutorials from the Microsoft Windows* OS Start menu, choose Intel System Studio 2016 > Documentation > Intel VTune Amplifier for Systems Documentation

Sample code is typically installed to <install-dir>\samples\<locale>\<programming_language>.

Release Notes

The Release Notes contain the most up-to-date information about the product, including a product description, technical support, and known limitations and issues.

This document also contains system requirements for installing the product. Before installation, the Release Notes document is located at the root level (same level as the installation script/executable) of the installation download package.

The Release Notes document is installed at: <install-dir>\documentation\<locale>\release_notes_amplifier_for_systems_windows.pdf

Installation Guide

The Installation Guide contains basic installation instructions for VTune Amplifier and post-installation configuration instructions for the various drivers and collectors.

The latest Installation Guide can be found on the Intel Developer Zone website.

Intel VTune Amplifier Help

The help is the primary documentation for the VTune Amplifier:

  • To view VTune Amplifier help from the standalone VTune Amplifier GUI Help menu: Choose Intel VTune Amplifier 2016 for Systems Help

  • To view VTune Amplifier help outside the VTune Amplifier GUI: Open the index.htm file installed at <install-dir>\documentation\<locale>\help.

Intel SoC Watch User's Guide (Android* | Windows* | target system)

This document provides detailed instructions on using the Intel Energy Profiler command line data collector, Intel SoC Watch, for power and energy analysis on Android, Windows and Linux target systems. For information on viewing and interpreting energy analysis data, see Intel VTune Amplifier Help > Energy Analysis User's Guide chapter.

SEP User's Guide

This document provides instructions on using the VTune Amplifier sampling collector (SEP) targeted for hardware event-based sampling analysis on resource-restricted systems.

Intel Processor Event Reference

This help provides reference information for Intel processor events used by the VTune Amplifier for hardware event-based sampling analysis. Most of this information is drawn from Intel processor information sources on the web. To access the Event Reference:

  • From the Visual Studio: Choose Help > Intel VTune Amplifier 2016 for Systems > Intel Processor Event Reference from the Help menu, or click the Help icon on the toolbar.
  • From the standalone VTune Amplifier GUI: Choose Intel Processor Event Reference from the Help menu, or click the Help icon on the toolbar.

Command line help

You can access general help for VTune Amplifier command line interface by entering the following command line:

  • amplxe-cl -help for help on basic action options

  • amplxe-cl -help <action-option> for help on a particular action option and its knobs

Web Resources

Legal Information

Intel, VTune and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.

* Other names and brands may be claimed as the property of others.

Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Copyright © 2013-2015, Intel Corporation. All rights reserved.

Getting Started with Intel® VTune™ Amplifier 2016 for Systems

$
0
0

Intel® VTune™ Amplifier for Systems Performance Profiler with Intel® Energy Profiler helps you speed up and optimize execution of your code on Linux* embedded platforms, Android* or Windows* systems providing the following types of analysis:

  • Performance analysis: Find serial and parallel code bottlenecks, analyze algorithm choices, GPU engines usage, and understand where and how your application can benefit from available hardware resources.

  • Intel Energy Profiler analysis: Analyze power events and identify those that waste energy.

VTune Amplifier for Systems is available as part of the Intel System Studio.

Select Your Host System to Get Started

Key Features

ALGORITHM ANALYSIS

HARDWARE EVENT-BASED SAMPLING ANALYSIS

  • Run Basic Hotspots analysis type to understand application flow and identify sections of code that get a lot of execution time (hotspots).

  • Run Concurrency analysis to estimate parallelization in your code and understand how effectively your application uses available cores.

  • Run Locks and Waits analysis to identify synchronization objects preventing effective utilization of processor resources.

  • Use the algorithm Advanced Hotspots analysis to extend Basic Hotspots analysis by collecting call stacks, context switches and analyze CPI (Cycles Per Instructions) metric.

  • Run General Exploration analysis to triage hardware issues in your application. This type collects a complete list of events for analyzing a typical client application.

  • Narrow down your hardware analysis by focusing on specific hardware issues, such as ineffective memory accesses, low bandwidth, and so on. VTune Amplifier analyzes your code, identifies issues and provides recommendations.

SOURCE ANALYSIS

GPU ANALYSIS

  • Double click a hotspot function to drill down to the source code and analyze performance per source line or assembler instruction. By default, the hottest line is highlighted.

  • For help on an assembly instruction, right-click the instruction in the Assembly pane and select Instruction Reference from the context menu.

  • Run CPU/GPU Concurrency analysis to identify code regions where your application is CPU or GPU bound.

  • For GPU-bound applications running on Intel HD Graphics, collect GPU hardware events to estimate how effectively the Processor Graphics are used.

  • Analyze hot Intel® Media SDK programs and OpenCL™ kernels running on a GPU. For OpenCL application analysis, use the Architecture Diagram to explore GPU hardware metrics per GPU architecture blocks.

CUSTOM ANALYSIS

ENERGY ANALYSIS

  • Select Custom Analysis branch in the analysis tree to create your own analysis configurations using any of the available VTune Amplifier data collectors.

  • Run your own custom collector from the VTune Amplifier to get the aggregated performance data, from your custom collection and VTune Amplifier analysis, in the same result.

  • Import performance data collected by your own or third-party collector into the VTune Amplifier result collected in parallel with your external collection. Use the Import from CSV button to integrate the external data to the *.amplxe result.

Use the Intel Energy Profiler to investigate high energy consumption on a platform with its summaries of CPU and GPU state residency, CPU and GPU processor frequency use, and correlated timelines of metrics that reflect platform energy use, such as thermals and bandwidth. The CPU sleep state timeline is annotated with wakeup reasons.

For the detailed list of product features, see Intel VTune Amplifier Help:Windows Host | Linux Host.

Remote Collection Modes

You can collect data on your Linux, Windows or Android system using any of the following modes:

  • (Linux and Android targets) Remote analysis via SSH/ADB communication with VTune Amplifier graphical and command line interface (amplxe-cl) installed on the host and VTune Amplifier target package installed on the remote target system. Recommended for resource-constrained embedded platforms (with insufficient disk space, memory, or CPU power).

  • (Linux and Windows targets) Native performance analysis with the VTune Amplifier graphical or command line interface installed on the target system. Analysis is started directly on the target system.

  • (Linux and Windows targets) Native hardware event-based sampling analysis with the VTune Amplifier's Sampling Enabling Product (SEP) installed on the target embedded system.

Legal Information

Intel, VTune and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.

* Other names and brands may be claimed as the property of others.

Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Copyright © 2013-2015, Intel Corporation. All rights reserved.

ICE with OpenMP workshare construct

$
0
0

Hello,

the following code leads to an internal compiler error:

module ifc_openmp_workshare_bug
  implicit none
  type t
     real, pointer :: u(:,:)
  end type t
contains
  subroutine sub (z, x, y)
    real,    intent(out) :: z(:,:)
    type(t), intent(in)  :: x
    type(t), intent(in)  :: y
!$omp parallel workshare
    z = x%u * y%u
!$omp end parallel workshare
  end subroutine sub
end module ifc_openmp_workshare_bug
% ifort -V -c -fopenmp ifort_omp.f90
Intel(R) Fortran Compiler XE for applications running on IA-32, Version 15.0.5.223 Build 20150805
Copyright (C) 1985-2015 Intel Corporation.  All rights reserved.
FOR NON-COMMERCIAL USE ONLY

 Intel(R) Fortran 15.0-1818
010101_13492

catastrophic error: **Internal compiler error: internal abort** Please report this error along with the circumstances in which it occurred in a Software Problem Report.  Note: File and line given may not be explicit cause of this error.
compilation aborted for ifort_omp.f90 (code 1)

Thanks,

Harald

 

Data in Array Constructor using multiplier has error

$
0
0

Can anyone help? I cannot get the array constructor data values to compile when using a multiplier on a constant.

This is an f77 conversion. Using MS VS 2003 and Intel V9.

The array used to look like:

      DATA ASTP1/0.,20.,40.,3*0.0/

I believed it should be like:

 Real, Parameter :: ASTP1(6) = (/0.,20.,40.,3*0.0/)

I also tried others  below that also did not work

 

 Real, Parameter :: ASTP1(6) = [0.,20.,40.,3*0.0]    

 Real, Parameter :: ASTP1(6) = [/0.,20.,40.,3*0.0/]

The issue is there are some arrays with 80*0..

That would be alot to do by hand.

Thanks Ken

 

 

 

 

Debbuger Installation Failure

$
0
0

I used the parallel_studio_xe_2016_composer_edition_for_fortran_setup.exe installer. During installation the message "The Intel(R) Debugger Extension for Intel(R) MIC Architecture cannot be installed. (Installation can continue; however, Intel(R) Debugger Extension for Intel(R) MIC Architecture will not be installed because it requires that Microsoft Visual Studio* 2012, 2013 or 2015 be installed. Refer to the Release Notes for more details.)" occured, see also attachment.

The installation is  on a Visual Studio 2013 shell, see attachment 2.

Except fur the debugger Visual Studio is installed and is running properly.  If "Start debug" is chosen (and in the compiler command line "debug:full " is set) the programme is compiled, linked and run and starts in debug mode, but it does not stop at any breakpoint. It runs as if not have been asked for debugging. In rare cases also a failure message occurs ("...to load an expression evaluator dll..."), see attachment 3.

Thanks in advance.

Gerd

Intel® Parallel Studio XE 2016 Composer Edition Fortran - Debug Solutions Release Notes

$
0
0

This page provides the current Release Notes for the Debug Solutions from Intel® Parallel Studio XE 2016 Composer Edition for Fortran Linux*, Windows* and OS X* products.

To get product updates, log in to the Intel® Software Development Products Registration Center.

For questions or technical support, visit Intel® Software Products Support.

For the top-level Release Notes, visit:

Table of Contents:

Change History

This section highlights important from the previous product version and changes in product updates.

Changes since Intel® Parallel Studio XE 2015 Composer Edition

  • Support for additional Fortran intrinsics added to GNU* GDB
  • Improved display of OpenMP* tasks with GNU* GDB

Product Contents

  • Linux*:
    • GNU* Project Debugger (GDB) 7.8:
      Command line for host CPU and Intel® Xeon Phi™ coprocessor, and Eclipse* IDE plugin for offload enabled applications.
  • OS X*:
    • GNU* Project Debugger (GDB) 7.8:
      Command line for CPU only.
  • Windows*:
    • Intel® Debugger Extension for Intel® Many Integrated Core Architecture (Intel® MIC Architecture)
    • Fortran Expression Evaluator (FEE) as extension to debugger of Microsoft Visual Studio*

GNU* GDB

This section summarizes the changes, new features, customizations and known issues related to the GNU* GDB provided with Intel® Parallel Studio XE 2016 Composer Edition.
 

Features

GNU* GDB provided with Intel® Parallel Studio XE 2016 Composer Edition and above is based on GDB 7.8 with additional enhancements provided by Intel. This debugger replaces the Intel® Debugger from previous releases. In addition to features found in GDB 7.8, there are several other new features:
  • Intel® Processor Trace (Intel® PT) support for 5th generation Intel® Core™ Processors:
    (gdb) record btrace pt
  • Support for Intel® Many Integrated Core Architecture (Intel® MIC Architecture)
  • Support for Intel® Transactional Synchronization Extensions (Intel® TSX) (Linux & OSX)
  • Register support for Intel® Memory Protection Extensions (Intel® MPX) and Intel® Advanced Vector Extensions 512 (Intel® AVX-512)
  • Data Race Detection (pdbx):
    Detect and locate data races for applications threaded using POSIX* thread (pthread) or OpenMP* models
  • Branch Trace Store (btrace):
    Record branches taken in the execution flow to backtrack easily after events like crashes, signals, exceptions, etc.
All features are available for Linux*, but only Intel® TSX is supported for OS X*.
 

Using GNU* GDB

GNU* GDB provided with Intel® Parallel Studio XE 2016 Composer Edition comes in different versions:
  • IA-32/Intel® 64 debugger:
    Debug applications natively on IA-32 or Intel® 64 systems with gdb-ia on the command line.
    A standard Eclipse* IDE can be used for this as well if a graphical user interface is desired.
  • Intel® Xeon Phi™ coprocessor debugger (only for Linux*):
    Debug applications remotely on Intel® Xeon Phi™ coprocessor systems. The debugger will run on a host system and a debug agent (gdbserver) on the coprocessor.
    There are two options:
    • Use the command line version of the debugger with gdb-mic.
      This only works for native Intel® Xeon Phi™ coprocessor applications.
      A standard Eclipse* IDE can be used for this as well if a graphical user interface is desired.
    • Use an Eclipse* IDE plugin shipped with Intel® Parallel Studio XE 2016 Composer Edition.
      This works only for offload enabled Intel® Xeon Phi™ coprocessor applications. Instructions on how to use GNU* GDB can be found in the Documentation section.

Documentation

The documentation for the provided GNU* GDB can be found here:
<install-dir>/documentation_2016/en/debugger/gdb-ia/gdb.pdf<install-dir>/documentation_2016/en/debugger/gdb-mic/gdb.pdf<install-dir>/documentation_2016/en/debugger/ps2016/get_started.htm

Known Issues and Changes

Not found: libtinfo.so.5

On some systems, using the GNU* GDB version that is provided by Intel fails due to a missing libtinfo.so.5 (e.g. SLES 11 SP3). If a package for libtinfo is not available, the following workaround can be applied:

$ sudo ln -s <path>/libncurses.so.5.6 <path>/libtinfo.so.5

As <path>, use the location of the system's ncurses library.

Safely ending offload debug sessions

To avoid issues like orphan processes or stale debugger windows when ending offload applications, manually end the debugging session before the application is reaching its exit code. The following procedure is recommended for terminating a debug session:
  1. Manually stop a debug session before the application reaches the exit-code.
  2. When stopped, press the red stop button in the tool-bar in the Intel® MIC Architecture-side debugger first. This will end the offloaded part of the application.
  3. Next, do the same for the CPU-side debugger.
  4. The link between the two debuggers will be kept alive. The Intel® MIC Architecture-side debugger will stay connected to the debug agent and the application will remain loaded in the CPU-side debugger, including all breakpoints that have been set.
  5. At this point, both debugger windows can safely be closed.

Intel® MIC Architecture-side debugger asserts on setting source directories

Setting source directories in the GNU* GDB might lead to an assertion.
Resolution:
The assertion should not affect debugger operation. To avoid the assertion anyway, don’t use source directory settings. The debugger will prompt you to browse for files it cannot locate automatically.

Debugger and debugged application required to be located on local drive (OS X* only)

In order to use the provided GNU* GDB (gdb-ia), it has to be installed on a local drive. As such, the entire Intel® Parallel Studio XE 2016 package has to be installed locally. Any application that is being debugged needs to be located on a local drive as well. This is a general requirement that’s inherent to GNU GDB with OS X*.

Debugging Fortran applications with Eclipse* IDE plugin for Intel® Xeon Phi™ coprocessor

If the Eclipse* IDE plugin for the Intel® Xeon Phi™ coprocessor is used for debugging Fortran applications, evaluation of arrays in the locals window might be incorrect. The underlying CDT applies the C/C++ syntax with brackets to arrays to retrieve their contents. This does not work for Fortran.
Solution: Use a fully qualified Fortran expression to retrieve the contents of arrays (e.g. with array sections like array(1:10)).
 
This section summarizes new features and changes, usage and known issues related to the Intel® Debugger Extension. This debugger extension only supports code targeting Intel® Many Integrated Core Architecture (Intel® MIC Architecture).
 

Features

  • Support for both native Intel® Xeon Phi™ coprocessor applications and host applications with offload extensions
  • Debug multiple Intel® Xeon Phi™ coprocessors at the same time (with offload extension)

Using the Intel® Debugger Extension

The Intel® Debugger Extension is a plug-in for the Microsoft Visual Studio* IDE. It transparently enables debugging of projects defined by  that IDE. Applications for Intel® Xeon Phi™ coprocessors can be either loaded and executed or attached to. This extension supports debugging of offload enabled code, using:
  • Microsoft Visual Studio* 2012
  • Microsoft Visual Studio* 2013
  • Microsoft Visual Studio* 2015

Documentation

The full documentation for the Intel® Debugger Extension can be found here:
<install-dir>\documentation_2016\en\debugger\ps2016\get_started.htm

Known Issues and Limitations

  • Disassembly window cannot be scrolled outside of 1024 bytes from the starting address within an offload section.
  • Handling of exceptions from the Intel® MIC Architecture application is not supported.
  • Starting an Intel® MIC Architecture native application is not supported. You can attach to a currently running application, though.
  • The Thread Window in Microsoft Visual Studio* offers context menu actions to Freeze, Thaw and Rename threads. These context menu actions are not functional when the thread is on an Intel® Xeon Phi™ coprocessor.
  • Setting a breakpoint right before an offload section sets a breakpoint at the first statement of the offload section. This only is true if there is no statement for the host between set breakpoint and offload section. This is normal Microsoft Visual Studio* breakpoint behavior but might become more visible with interweaved code from host and Intel® Xeon Phi™ coprocessor. The superfluous breakpoint for the offload section can be manually disabled (or removed) if desired.
  • Only Intel® 64 applications containing offload sections can be debugged with the Intel® Debugger Extension for Intel® Many Integrated Core Architecture.
  • Stepping out of an offload section does not step back into the host code. It rather continues execution without stopping (unless another event occurs). This is intended behavior.
  • The functionality “Set Next Statement” is not working within an offload section.
  • If breakpoints have been set for an offload section in a project already, starting the debugger might show bound breakpoints without addresses. Those do not have an impact on functionality.
  • For offload sections, using breakpoints with the following conditions of hit counts do not work: “break when the hit count is equal to” and “break when the hit count is a multiple of”.
  • The following options in the Disassembly window do not work within offload sections: “Show Line Numbers”, “Show Symbol Names” and “Show Source Code”
  • Evaluating variables declared outside the offload section shows wrong values.
  • Please consult the Output (Debug) window for detailed reporting. It will name unimplemented features (see above) or provide additional information required to configuration problems in a debugging session. You can open the window in Microsoft Visual Studio* via menu Debug->Windows->Output.
  • When debugging an offload-enabled application and a variable assignment is entered in the Immediate Window, the debugger may hang if assignments read memory locations before writing to them (for example, x=x+1). Please do not use the Immediate Window for changing variable values for offload-enabled applications.
  • Depending on the debugger extensions provided by Intel, the behavior (for example, run control) and output (for example, disassembly) could differ from what is experienced with the Microsoft Visual Studio* debugger. This is because of the different debugging technologies implemented by each and should not have a significant impact to the debugging experience.

Fortran Expression Evaluator (FEE) for debugging Fortran applications with Microsoft Visual Studio*

Fortran Expression Evaluator (FEE) is a plug-in for Microsoft Visual Studio* that is installed with Intel® Visual Fortran Compiler. It extends the standard debugger in Microsoft Visual Studio* IDE by handling Fortran expressions. There is no other change in usability.

Known Issues and Limitations

Debugging might fail when only Microsoft Visual Studio 2013/2015* is installed

For some FEE functionality the Microsoft Visual Studio 2012* libraries are required. One solution is to install Microsoft Visual Studio 2012* in addition to Microsoft Visual Studio 2013/2015*. An alternative is to install the "Visual C++ Redistributable for Visual Studio 2012 Update 4" found here.
If you installed Intel® Parallel Studio XE 2016 on a system without any Microsoft Visual Studio* version available, a Microsoft Visual Studio 2013* Shell (incl. libraries) will be installed. It might be that FEE does not work in that environment. Please install the redistributable package mentioned above in addition to enable FEE. A future update will solve this problem for the installation of the shell.

Debugging mixed language programs with Fortran does not work

To enable debugging Fortran code called from a .NET managed code application in Visual Studio 2012 or later, unset the following configuration:
Menu Tools->Options, under section Debugging->General, clear the "Managed C++ Compatibility Mode" or "Use Managed Compatibility Mode" check box

Debug Options Compatibility Mode

For any managed code application, one must also check the project property Debug > Enable unmanaged code debugging.

FEE Truncates Entries in Locals Window

To increase debugging performance, the maximum number of locals queried by the debug engine is limited with Intel® Parallel Studio XE 2016 and later releases. If a location in the source code has more than that number of locals, they are truncated and a note is shown:

Note: Too many locals! For performance reasons the list got cut after 500 entries!

The threshold can be controlled via the environment variable FEE_MAX_LOCALS. Specify a positive value for the new threshold (default is 500). A value of -1 can be used to turn off truncation entirely (restores previous behavior) - but at the cost of slower debug state transitions. In order to take effect, Microsoft Visual Studio* needs to be restarted.

Problem with Debugging C# Applications

If Microsoft Visual Studio 2015* is used, debugging of C# applications might cause problems, i.e. evaluations like watches won't work.If you experience issues like that, try to enable "Managed Compatibility Mode". More details how to enable it can be found here:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/10/16/switching-to-managed-compatibility-mode-in-visual-studio-2013.aspx

The problem is known and will be fixed with a future version.

Attributions

This product includes software developed at:

GDB – The GNU* Project Debugger

Copyright Free Software Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.

This program is free software; you can redistribute it and/or modify it under the terms and conditions of the GNU General Public License, version 2, as published by the Free Software Foundation.

This program is distributed in the hope it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.

GNU* Free Documentation License

Version 1.3, 3 November 2008

 

Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. <http://fsf.org/>

 

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

 

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

 

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

The "publisher" means any person or entity that distributes copies of the Document to the public.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

 

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

 

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

 

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.

C. State on the Title page the name of the publisher of the Modified Version, as the publisher.

D. Preserve all the copyright notices of the Document.

E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.

H. Include an unaltered copy of this License.

I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

 

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

 

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

 

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

 

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

 

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.

 

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.

 

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document.

 

11. RELICENSING

"Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A "Massive Multiauthor Collaboration" (or "MMC") contained in the site means any set of copyrightable works thus published on the MMC site.

"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.

"Incorporate" means to publish or republish a Document, in whole or in part, as part of another Document.

An MMC is "eligible for relicensing" if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.

The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.

 

Disclaimer and Legal Information

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to:  http://www.intel.com/design/literature.htm

Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. Go to:
http://www.intel.com/products/processor_number/

MPEG-1, MPEG-2, MPEG-4, H.261, H.263, H.264, MP3, DV, VC-1, MJPEG, AC3, AAC, G.711, G.722, G.722.1, G.722.2, AMRWB, Extended AMRWB (AMRWB+), G.167, G.168, G.169, G.723.1, G.726, G.728, G.729, G.729.1, GSM AMR, GSM FR are international standards promoted by ISO, IEC, ITU, ETSI, 3GPP and other organizations. Implementations of these standards, or the standard enabled platforms may require licenses from various entities, including Intel Corporation.

BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino Inside, Cilk, Core Inside, i960, Intel, the Intel logo, Intel AppUp, Intel Atom, Intel Atom Inside, Intel Core, Intel Inside, Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel Sponsors of Tomorrow., the Intel Sponsors of Tomorrow. logo, Intel StrataFlash, Intel Viiv, Intel vPro, Intel XScale, InTru, the InTru logo, InTru soundmark, Itanium, Itanium Inside, MCS, MMX, Moblin, Pentium, Pentium Inside, skoool, the skoool logo, Sound Mark, The Journey Inside, vPro Inside, VTune, Xeon, and Xeon Inside are trademarks of Intel Corporation in the U.S. and other countries.

* Other names and brands may be claimed as the property of others.

Microsoft, Windows, Visual Studio, Visual C++, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Java is a registered trademark of Oracle and/or its affiliates.

Copyright (C) 2008–2015, Intel Corporation. All rights reserved.

  • Développeurs
  • Professeurs
  • Étudiants
  • Apple OS X*
  • Linux*
  • Microsoft Windows* (XP, Vista, 7)
  • Microsoft Windows* 10
  • Microsoft Windows* 8.x
  • Fortran
  • Intel® Parallel Studio XE Composer Edition
  • PC portable
  • Bureau
  • URL
  • Array Declaration

    $
    0
    0

    Hi All,

    For a Fortran array, Is there any compiler specific parameter to set the array lower bound to zero? Because Linux considers the lower bound as one always.


    link error

    $
    0
    0

    Bonjour Fortran fellows,

    My projects used to link and work fine. Then suddenly I get the following error.

    So I go to "project properties", change the default libs, try again, most of the times it does not work, but sometimes it links fine, but only one time.

    My other projects with exactly the same parameters do link fine.

    Thanks in advance for your help

    Jean-Marc  

     

    Error      23           fatal error LNK1169: one or more multiply defined symbols found        c:\casal\execut/interface.exe 

    Error      13           error LNK2005: _YIELDQQ already defined in ifconsol.lib(for_m_console.obj)  ifqwin.lib(qwkyield.obj)               

    Error      6             error LNK2005: _RegisterGetUnitQQ already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgact.obj) 

    Error      5             error LNK2005: _RegisterGetHandleQQ already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgact.obj) 

    Error      4             error LNK2005: _ChangeQWINCP already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgmbcs.obj)            

    Error      8             error LNK2005: __wgsetactive already defined in ifconsol.lib(for_m_console.obj)        ifqwin.lib(qwgact.obj)               

    Error      20           error LNK2005: __wgopen already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgopen.obj)            

    Error      9             error LNK2005: __wggetactive already defined in ifconsol.lib(for_m_console.obj)        ifqwin.lib(qwgact.obj)               

    Error      22           error LNK2005: __scrolltextwindow already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgtext.obj)               

    Error      16           error LNK2005: __QWINWrite already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgread.obj)              

    Error      12           error LNK2005: __QWINTGethFrame already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwintern.obj)             

    Error      18           error LNK2005: __QWINSetSize already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgsize.obj)

    Error      17           error LNK2005: __QWINSetIOFOCUS already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgread.obj)              

    Error      3             error LNK2005: __QWINRegisterInit already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwkentry.obj)            

    Error      1             error LNK2005: __QWINRegisterEnd already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwkentry.obj)            

    Error      15           error LNK2005: __QWINRead already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgread.obj)              

    Error      2             error LNK2005: __QWINNiceExit already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwkentry.obj)            

    Error      14           error LNK2005: __QWINMsgBox already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwkwnd.obj)              

    Error      19           error LNK2005: __QWINGetSize already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgsize.obj)

    Error      10           error LNK2005: __QWINGethWnd already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgact.obj) 

    Error      11           error LNK2005: __QWINGetDefaultWindow already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgact.obj) 

    Error      7             error LNK2005: __inchar already defined in ifconsol.lib(for_m_console.obj)    ifqwin.lib(qwgact.obj) 

    Error      21           error LNK2005: __displaycursor already defined in ifconsol.lib(for_m_console.obj)                ifqwin.lib(qwgtext.obj)               

    Getting Started with Intel® Advisor 2016

    $
    0
    0

    Intel® Advisor 2016 provides two tools to help ensure your Fortran, C and C++ native/managed applications take full performance advantage of today's processors:

    • Vectorization Advisor is a vectorization analysis tool that lets you identify loops that will benefit most from vectorization, identify what is blocking effective vectorization, explore the benefit of alternative data reorganizations, and increase the confidence that vectorization is safe.

    • Threading Advisor is a threading design and prototyping tool that lets you analyze, design, tune, and check threading design options without disrupting your normal development.

    Intel® Advisor 2016 is available as part of the:

    • Intel® Parallel Studio XE Professional Edition

    • Intel® Parallel Studio XE Cluster Edition

    If you do not already have access to the Intel® Advisor 2016 or to Version 15.0 or higher of an Intel compiler, download an evaluation copy from http://software.intel.com/en-us/articles/intel-software-evaluation-center/. (Use an Intel compiler to get more benefit from the Vectorization Advisor  Survey Report.)

    Choose Platform and Tool/Feature to Continue

    Choose Vectorization Advisor-Linux* OS  Choose Vectorization Advisor-Windows* OS  Choose Threading Advisor-Linux* OS  Choose Threading Advisor-Windows* OS  Choose CLI & MPI  Choose Documentation & Resources

    Installation problems regarding Visual Studio 2010

    $
    0
    0

    Dear all,

    sorry this probably will come as a very easy or stupid question to you, yet I still need some help.

    In order to use subroutines in Abaqus I need a Fortran Compiler, like in the "Intel Parallel Studio XE 2015 Composer for Fortran", which I just installed. Furthermore I need Microsoft Visual Studio 2010 or newer.

    I thought those two will come together when installing the Parallel Studio XE2015? Or ist it just the express Version?

    When opening the just installed Microsoft Visual Studio 2010 folder, coming with the XE2015, the for me essential  file
    vcvarsall.bat, which should be located in "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC" is missing.

    Do I need a professional Version of Microsoft Visual Studio 201x or did I do sth wrong? can I get the missing file from somewhere else?

    Thanks a lot and best regards
     

     

    Bogus error: error #7367: The data value NULL() can only be assigned to a Fortran POINTER.

    $
    0
    0

    The following code compiles with gfortran but not ifort V15:

    module cu

    type db_node_struct

      real, pointer :: ptr(:) => null()

    end type

     

    type db_struct

      type (db_node_struct) :: node(15) = db_node_struct() 

    end type

     

    type aaa

      type (db_struct) :: db = db_struct()

    end type

     

    end module

     

    The generated error is:

    erpsim1:~/linux_lib/test> ifort -c cu.f90

    cu.f90(12): error #7367: The data value NULL() can only be assigned to a Fortran POINTER.

      type (db_struct) :: db = db_struct()

    ^

    compilation aborted for cu.f90 (code 1)

    Unable to useIntel® Parallel Studio XE 2016 Professional Edition for Fortran Windows

    $
    0
    0

    I am using Windows-10

    I recently downloaded, Intel® Parallel Studio XE 2016 Professional Edition for Fortran Windows, to evaluate the package. I also downloaded and installed Microsoft Visual Studio 2015.

    After installation of of the Intel Parallel Studio for Fortran, I am unable to use it within Visual Studio 2015. I do not see any option for creating or selecting projects.

    Per the instructions on getting started with fortran, after installation, I used the following steps.

    1. From a command prompt or script, cd to:
      <install-dir>\IntelSWTools\parallel_studio_xe_2016.<update number>.<package number>\bin
      By default, <install-dir> is C:\Program Files (x86), or C:\Program Files
    2. Run psxevars.bat.intel64
    3. I get the error message: ERROR: Visual Studio 2010, 2012 or 11 is not found in the system.

    My questions are:

    1. do I need to get Visual Studio 2010, 2012 or 11?
    2. If this product is compatible with Visual Studio 2015, how do I get them integrated?
    3. I am attaching screen shots of the error message as well as the opening pane for Visual Studio 2015

    I will appreciate all your help in getting me started so I can start evaluating the software package. Thank you for your help.

    Animesh

    adey@vextec.com

     

     

     

    Fichier attachéTaille
    Téléchargerscreenshots.pdf193.99 Ko
    Viewing all 3108 articles
    Browse latest View live


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