Search

Search Results for:

Search Results: 191,000

  1. This USE statement is not positioned correctly within the scoping unit.

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268717

    Jul 24, 2007 ... I keep getting this error, and I have no idea why. The program is in a very standard structure:

  2. Basic Concepts

    https://software.intel.com/sites/landingpage/opencl/optimization-guide/Basic_Concepts.htm

    Computing unit - An OpenCL* device has one or more compute units. A work- group executes on a single compute unit. A compute unit is composed of one or ...

  3. Maximum number of Fortran units

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/299178

    Is there a maximum for the number of Fortran units? I am doing an INQUIRE on units 7-99, and the inquire on unit 39 gives: forrtl: severe (157): ...

  4. iforrtl: severe (67): input statement requires too much data, unit 20 ...

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/703458

    a.out forrtl: severe (67): input statement requires too much data, unit 20, file /hpcs/ bipink/LES/cloud_phy/mixing_data Image PC Routine Line ...

  5. forrtl: severe (29): file not found, unit 89 ?! How to solve this error?

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/269187

    Nov 26, 2008 ... Thanks. forrtl: No such file or directoryforrtl: severe (29): file not found, unit 89, file /Users/cks/CNCLASS/fort.89 ===I post the process and error ...

  6. Error: This name does not match the unit name. [DO_COMBINE]

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/276759

    Aug 20, 2007 ... Please help me identify the source of this error. My code is as follows: program do_combine use decarrays implicit none !include ...

  7. iforrtl: severe (67): input statement requires too much data, unit 60

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268578

    Nov 27, 2006 ... iforrtl: severe (67): input statement requires too much data, unit 60 ... if (exist) then . open (UNIT, file=file_name(1:len), status='old',

  8. Nehalem Performance Monitoring Unit Programming Guide

    https://software.intel.com/sites/default/files/m/5/2/c/f/1/30320-Nehalem-PMU-Programming-Guide-Core.pdf

    Programming. Guide. Intel® Microarchitecture Codename Nehalem Performance . Monitoring Unit Programming Guide. (Nehalem Core PMU) ...

  9. How to inspect Visual Studio 2013 unit tests with Intel Inspector XE ...

    https://software.intel.com/en-us/forums/intel-inspector-xe/topic/703858

    Nov 24, 2016 ... Hi, I am trying to inspect Visual Studio 2013 unit tests in mixed layer. The unit test (CLI layer) project generates a dll which calls native dlls.

  10. Texture Unit Load | Intel® Software

    https://software.intel.com/en-us/node/597522

    Metric Description The Texture Unit Load metric represents the percentage of the time that the texture units are busy. Improving Performance Use the following ...

  11. OPEN(NEWUNIT Set Unit To Positive Value

    https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/401433

    I have a large program that reads in an input file that contains a list of additional input files and a unit number. I like to change the code so that it ...

  12. Intel® Xeon Phi™ Coprocessor Vector Microarchitecture | Intel ...

    https://software.intel.com/en-us/articles/intel-xeon-phi-coprocessor-vector-microarchitecture

    May 31, 2013 ... The VPU receives its instructions from the core arithmetic logic unit (ALU) and receives the data from the L1 cache by a dedicated 512- bit bus.

  13. Smooth Rectifier Linear Unit (SmoothReLU) | Intel® Software

    https://software.intel.com/en-us/node/681939

    Smooth Rectifier Linear Unit (SmoothReLU). The SmoothReLU function is defined as f( x ) = log (1 + exp( x )). Problem Statement. Given n feature vectors x 1 ...

  14. KNL DRAM RAPL Energy Unit ?

    https://software.intel.com/en-us/forums/intel-many-integrated-core/topic/706082

    On my Xeon Phi 7250 systems, the "energy unit" that I read from MSR_RAPL_POWER_UNIT register works out to 61.04 micro-Joules. This is ...

  15. Visual Studio 2013/2015 built in native unit tests aren't discovered ...

    https://software.intel.com/en-us/forums/intel-c-compiler/topic/628018

    Apr 24, 2016 ... Does the Intel compiler support compiling native unit test projects using Microsoft's built in unit testing framework? I can't find it listed as an ...

  16. Integer Unit vs Floating Point Unit

    https://software.intel.com/en-us/forums/software-tuning-performance-optimization-platform-monitoring/topic/605167

    Dec 17, 2015 ... My questions are: why the floating point has better speed-up than integer? how many fpu and integer unit of intel core i7 4790? Thanks in ...

  17. Formatted OPEN don't work in Linux?

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/268953

    Here is my code, work in windows but not in linux: program circle CHARACTER* 1 A INTEGER IOS OPEN(UNIT = 789, & FILE= 'charlie.dem', ...

  18. Code Sample: Storage Unit Flood Detector in JavaScript* | Intel ...

    https://software.intel.com/en-us/articles/storage-unit-flood-detector

    Nov 6, 2015 ... This storage unit flood detector application is part of a series of how-to Intel® Internet of Things (IoT) code sample exercises using the Intel® IoT ...

  19. Runtime error message: no data-edit-descriptor to match a data-item ...

    https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/269348

    forrtl: severe (105): there is no data-edit-descriptor to match a data-item in the I/O list, unit -5, file Internal Formatted Write I compiled with:mpif90 ...

  20. Standardizing Feature Columns and Scaling to Unit Variance ...

    https://software.intel.com/en-us/node/674783?language=de

    Performs these tasks: Standardize each feature column by removing the mean and scaling to unit variance. Scale the column to fit within the range 0 to 255.

For more complete information about compiler optimizations, see our Optimization Notice.