Microsoft Windows* 8.x

values of parameters in ENTRY

Working with :


1>------ Build started: Project: Xdsim10, Configuration: Debug Win32 ------

1>Compiling with Intel(R) Visual Fortran Compiler XE [IA-32]...


in Visual Studio Professional 12 - Update 4.

In debugging, values of parameters passed in ENTRY statements are not displayed.

Quick watch notification is : 'undefined variable' or something like that.

Strategies for Battery-Friendly Intel® RealSense™ Applications

For mobile platforms that run on battery power, the longer the device can run between charges, the more desirable the user experience. This paper presents several techniques for developing power efficient applications using the Intel® RealSense™ Software Development Kit (SDK), primarily targeting battery-powered devices such as laptops and tablets.
  • Desarrolladores
  • Microsoft Windows* 10
  • Microsoft Windows* 8.x
  • Desarrollo de juegos
  • Tecnología Intel® RealSense™
  • Windows*
  • C/C++
  • SDK de Intel® RealSense™
  • Tecnología Intel® RealSense™
  • Intel RealSense
  • Intel RealSense SDK
  • improve power efficiency of applications
  • Experiencia del usuario y diseño
  • Compiler errors with parameterized types using defined assignment and - operator

    module TestParamTypeMod
       integer, parameter :: DP =  SELECTED_REAL_KIND(13)
       type DoubleDif(n)
          integer, len :: n
          real(DP) :: v
          real(DP) :: d(n)
       end type
       interface assignment(=)
          module procedure ass_D_Dpdif, ass_Dpdif_Dpdif
       end interface
       interface operator(-)
          module procedure sub_Dpdif_Dpdif
       end interface
    pure elemental subroutine ass_D_Dpdif(b, a)
       real(DP), intent(in) :: a
       type(DoubleDif(*)), intent(inout) :: b
       b%v = a
       b%d = 0.0_DP
    end subroutine

    Character String Length Problems

    To the Intel Forum,

    I'm converting a Compaq Fortran code to compile and run under Intel Fortran XE 2013 SP1 (M/S Windows 7)  However, I seem to be having some very basic Character String length problems when using the debug tool under Intel Fortran 2013. For example:


    ACS = 'Pitch'

    give an error, or even inserting a character from one string into another with I=3,

    WFILE(1:1) = NAME(I:I)

    also generates an error under Debug step through.

    Q about debugging difficulty

    I am debugging a program, and I get a breakpoint, apparently because of an out-of-range subscript.

    Anyway, when I open the relevant subroutine, isn't it supposed to SHOW me where the breakpoint occurred?

    (It is mentioned in the OUTPUT pane.) but it doesn't show me where in the CODE listing.

    I also wanted to put the cursor on some variables that would show me their contents

    so I can track down why it occurred. But I don't get anything regarding what is stored in any of them.

    Fortran 14.1 command prompt redefining environment variable COMMONPROGRAMFILES

    Has anyone noticed an issue with the intel 14.1 command prompt (either 32 or 64 bit) and having the COMMONPROGRAMFILES environment variable changed from the windows default (C:\Program Files\Common Files) to C:\Program Files (x86)\Common Files?  If a try to run some other software that uses the default environment variable from the intel prompt it does not function and I must switch to another prompt that does not support the fortran.  So on my system I have the following set by default

    C:\Program Files\Common Files

    RANDOM_NUMBER, RANDOM_SEED dependencies?

    I am observing some unexpected behavior  from RANDOM_NUMBER.   I am getting differences between sequences generated by RANDOM_NUMBER after using RANDOM_SEED to set the seed.   I am writing to see if anyone can confirm or deny that Intel RANDOM_NUMBER sequences only depend upon calls to either RANDOM_NUMBER or RANDOM_SEED, and there is no dependency,  either on other Fortran routines or C/C++/C# libraries?



    Suscribirse a Microsoft Windows* 8.x