Reference Number : DPD200141726 Version : 11.1 and earlier Product : Intel(R) Visual Fortran Compiler Professional Edition for Windows* Operating System : Microsoft Windows XP*, Microsoft Windows Vista* Problem Description : Intermitent Errors were observed when building multi-project solutions under Visual Studio* on multi-core systems. Examples of errors reported: catastrophic error: Unable to read ‘filename’ error #5102: Cannot open include file ‘filename’ Microsoft Visual Studio has encountered a problem and needs to close All files flagged by the errors were present and accessible. Errors occurred on both Windows XP* and Vista* and on Visual Studio 2005* and 2008*. Errors were not observed on single core systems. Given the above information it was concluded that this was a parallel build issue. Visual Studio* will by default set the maximum number project builds to be performed in parallel to the number of cores on the system on which it was installed. Setting tools> Options…> Project and Solutions> Build and Run> maximum number of project builds to 1 eliminates the build errors. It should also be noted that the errors only occur when devenv is invoked from the command line. Build errors do not occur when building under the IDE. Resolution Status : This issue has been fixed in Intel(R) Visual Fortran Compiler Professional Edition for Windows* version 11.1 Update 5 (w_cprof_p_11.1.060)
Here is the original:
Intermitent Errors Occurring When Building under Visual Studio*
Cloud Research Open Cirrus is an open cloud computing research testbed, jointly formed by Intel, HP and Yahoo. With more than 10 cloud test beds worldwide, Open Cirrus is designed to support research into the design, provisioning, and management of services at a global, multi-datacenter scale. Intel is also an affiliate member of UC Berkeley’s RAD Lab, a research group focused on leveraging powerful techniques from statistical machine learning (SML), as well as recent insights from networking and distributed systems.
Here is the original post:
Intel Cloud Builder Cloud Research
Manycore Testing Lab – Cloud computing on 32 cores for Academia Bringing students a competitive advantage through access to manycore computing.
See original here:
Intel Manycore Testing Lab
Section 3.1.3 of the Release Notes for Version 3.0 of Intel® Graphics Performance Analyzers (Intel® GPA) includes information on which graphics drivers are required for use with the product. Since the initial release of Version 3.0 of Intel GPA, new versions of the graphics drivers have been released that fix a number of issues in the interaction between Intel GPA and the graphics device.
Read more from the original source:
Clarification on graphics device driver requirements for Intel® GPA 3.0
Symptom : When the user ran Call graph to statically instrument EXE or some DLLs, met error message such as ” Error in module ###.dll – Module is an instrumented module ” Cause : Call graph copies (saves) original user’s EXE/DLLs to Call graph’s cache directory first, then put instrumented EXE/ DLLs in their original directories respectively. After doing data collection, copies original modules from cache directory to original directories, and keeps instrumented modules to Call graph’s cache directory. Next time to run Call graph again, user’s modules will not be instrumented (assume that source code are not changed, and don’t rebuild modules), get them from Call graph’s cache to save time.
Read the original here:
Get error message “Module is an instrumented module” when using Call graph data collector
This article contains a training material (in PDF format) on Intel® MKL Sparse Solvers which includes details of PARDISO/DSS, Iterative Solvers features and performance.
Original post:
Intel® MKL Sparse Solvers Training Material
Problem : In Intel® IPP UIC JPEG decoder sample, CJPEGDecoder::ParseDQT , there is a validity check on the quantization table ID as below and causes an access violation. if((id & 0×0f) > MAX_QUANT_TABLES) Environment : Intel® IPP 6.1 for Windows Root Cause : The quantization table ID is off by one which causes the access violation. Resolution : The line if((id & 0×0f) > MAX_QUANT_TABLES) should be changed to if((id & 0×0f) > = MAX_QUANT_TABLES) becuase the id is used to index an array of size MAX_QUANT_TABLES . This bug has been fixed and the fix will be available in Intel® IPP 7.0 beta onwards
Here is the original post:
UIC JPEG decoder in Intel® IPP 6.1 causes access violation
Reference Number: DPD200090099 Version: Intel® MKL 10.2 ( all updates 1,..4) Operating Systems: Windows (64 bit) and Linux (64 bit) Problem Description : If the program contains calls to any function from the VML library (for example vdSub (n, a, b, y) which performs element by element subtraction of vector b from vector a) and it runs on Intel(R) Core(TM)2 Duo CPU E8400 or Intel Core2 Duo T9600 the program causes signal SIGILL, Illegal instruction.
View original post here:
Illegal instruction Intel(R) Core(TM)2 Duo CPU E8400
Abstract Synchronization is often an expensive operation that can limit the performance of a multi-threaded program.
Read more from the original source:
Use Thread-local Storage to Reduce Synchronization
The following tables show the use cases, supported processors, operating systems, and tool suite contents for the Intel® Application Software Development Tool Suite for Intel Atom™ Processor and Intel® Embedded Software Development Tool Suite for Intel Atom™ Processor. Both suites are recommended for the following segments using Intel® Atom™ processors
Read the original:
Intel® Tools for Intel® Atom™ Processors – Market Segment Analysis
