Intel® Parallel Inspector Update 1 has realized this feature.

After the user has installed the product, open a Command Prompt window, run

C:\Program Files\Intel\Parallel Studio\Inspector\insp-vars.bat

Thus the environment for command line has been settled down, now can use insp-cl

The user can run "insp-cl -help" to be familiar with the syntax of command.

Usage:

insp-cl <-action-option [-modifier-option] [[--] target [target options]]

Action-option contains：collect, collect-list, command, command-list, finalize, help, version

Modifier-option contains：[no-]discard-suppressed-problem, log-dir, option-file, result-dir, return-app-exitcode, search-dir, suppression-file, user-data-dir, verbose

Below are some examples to use insp-cl: 

insp-cl -collect-list      [List all checking modes, now are mi1-mi4, ti1-ti4]

insp-cl -collect mi2 Banner.exe [Generate results in sub-directory, refer to Insp-cl.txt]

insp-cl -collect mi3 -result-dir r009mi3 Banner.exe [Generate results in specified sub-directory]

insp-cl -collect mi3 Banner.exe  [First time run it]

insp-cl -create-suppression-file mySup [Generate a suppression file, based on previous run]

insp-cl -collect mi3 -suppression-file mySup Banner.exe [Use suppression file to run, but don't report errors which already are in suppression file]

Q:  SSE2 is a standard and it is supported by AMD. Why is it set as "Intel Processor Specific
     Optimization?
A:  The Intel® C++ compiler can generate code targeting any processor with SSE2 instruction set support,
     using /Qax:SSE2 or can generate code that is optimized for Intel processors with SSE2 support using /QxSSE2.
     The latter offers more optimizations and it does a cpu check when the application is executed.

Q:  Do you need to #include<omp.h> to be able to use #pragma omp?
A:  No, but you need to include omp.h if you want to call the OpenMP APIs such as omp_get_num_threads(),
     omp_thread_num(), etc.

Q:  If I am using omp dlls, will concurrent omp applications (processes) compete for CPU resources the
     same way as it is when I use static omp libraries?
A:   Testing shows there is practically no performance advantage to linking mulitple processes with the static OpenMP runtime, as opposed to linking with the dynamic runtime (uses DLLs), which is the default.  But in either linking scenario, you have to be careful not to oversubscribe the machine if using multiple OpenMP processes.  With multiple, independent OpenMP processes running on a host, the OpenMP runtime library execution mode should be 'throughput' (environment variable KMP_LIBRARY), which is the default.  On the other hand, if you have a dedicated host, the runtime library execution mode should be 'turnaround', which will minimize the execution time of a single OpenMP process.

Q:  How is the binary compatibility between the Intel compiler and the Visual Studio compiler maintained when VS only supports OpenMP 2.5?
A:  If you want to use any new features in OpenMP 3.0, you have to use the Intel® Parallel Composer, but if you only
     use the features from OpenMP 2.5, you can use Visual C++ 2005 or 2008 or the Intel Parallel Composer. Please
     refer to this knowledge base article for more information at:
           http://software.intel.com/en-us/articles/how-to-use-intelr-compiler-openmp-compatibility-libraries-on-windows/

 Q:  May be it's better to use 4 threads for 2 cores? (i.e. Number threads = Number Cores * 2?
 A:  Probably not unless the machine is hyperthreaded, and hyperthreading is enabled in the BIOS; otherwise you will
      oversubscribe the machine.  In general shouldn't give any OpenMP process more than the number of machine logical threads (number-of-processors * number-of-cores/processor * number-of-threads/core), and in fact you might find it better to limit the total of number of OpenMP threads to something less.  Testing shows that the
      performance penalty by oversubscribing the machine can be severe.  In general, it is OK to use all the machine's logical threads for one OpenMP process (and this is the default, unless you explicitly change the number by setting OMP_NUM_THREADS or by calling omp_set_num_threads()), but depending on your host usage scenario, you should set the environment for 'throughput' (multiple OpenMP processes running) or 'turnaround' (single, dedicated OpenMP process).

Q:  What is the difference between using omp parallel task versus using omp parallel sections calling a task?
A:  Calling a task within a section just creates extra overhead and cannot control and synchronize the tasks since
     each parallel section is independent of each other. OpenMP 3.0 tasking is more flexible and efficient compared to 
     using parallel sections.  With parallel sections, there is no way to coordinate the task in each section, so it is not 
     possible to determine whether one section will be executed before another, regardless of which section comes first 
     in the program source.  On the other hand, the task directive can take an "if" clause to cause the task to be
     executed immediately or be deferred; a thread can be "hard wired" to a task (called "tied"), or can be "untied",
     which allows any available thread in the thread pool to start executing the task.  Tasking has much better 
     performance and scalability for nested parallel and recursive algorithms, compared to parallel sections.  There is
     much more overhead creating and destroying the nested parallel regions (parallel sections tasking), versus
     executing tasks which are all created by a single parallel region containing a task directive.  You can control the total number of threads (OMP_NUM_THREADS) with tasking, whereas with nested parallel regions (sections), with each newly created region you get OMP_NUM_THREADS new threads, and that can easily oversubscribe the host.

Q:  Do you have a favorite textbook about OpenMP that you recommend?
A:  Please look at the "Related Information" section in the product user guide where there is a mention of associated 
     Intel Documents. A good recommended book to look at: "Using OpenMP: Portable Shared Memory Parallel
     Programming" by Barbara Chapman, Gabriele Jost, and Ruud van der Pas

The following table can help you decide which tool to use:

	Intel® Parallel Inspector	Intel® Thread Checker
Threading errors - Data races and Deadlocks	√	√
Does not require special build or source code	√	√
Memory errors	√
Easier to learn and reuse	√
Low overhead analysis	√
Improved scalable analysis without serializing the app	√
Windows* standalone		√
Linux* support		√
Licensing	Single User	Single User & Floating
Support	forum support premier support option	unlimited premier support & 1 year product updates

A: No. The Intel Parallel Studio is targeting Microsoft* Visual C++ developers.
If your program uses Fortran language, you should use the following tools:

• Intel Visual Fortran Compiler Professional Edition for Windows
• Intel VTune™ Analyzer with Intel Thread Profiler for Windows
• Intel Thread Checker for Windows*

Please visit http://software.intel.com/en-us/articles/intel-software-evaluation-center/ for more information.

A: Yes, but most are already ignored by default. 

Suppression can be used to suppress any errors reported in any DLL, source file, or function.  See the Defining Private Suppression Rules topic in the Parallel Inspector help for more information.

A: The Intel Parallel Studio can be used with Visual Studio 2005* standard edition or above, or Visual Studio 2008* standard edition or above.

Please see the Release Notes at http://software.intel.com/sites/products/documentation/studio/studio/en-us/2009/start/release_notes_studio.pdf for complete information.

A: OpenMP and the native thread can be used together.
Be aware of the possibility of thread over subscription. You can control the number of threads for OpenMP to use from an environment variable or programmatically in the code.

There's one nice article talking about this at http://software.intel.com/en-us/articles/intel-threading-building-blocks-openmp-or-native-threads/

A: If the program can run within Microsoft Visual Studio, the Intel Parallel Amplifier should work. It might be a bug.
To report any issue about Intel Parallel Studio, please visit our Studio Forum http://software.intel.com/en-us/forums/intel-parallel-studio/.

A: No.
Please use the Intel VTune Analyzer with Intel Thread Profiler for Windows*.

A: No, that is not supported by the Intel Parallel Studio.

The cross compiling for a different architecture of the same OS is supported, but it's not supported for a different OS. i.e. you can cross compiling the application for Intel 64 Windows on an IA-32 Windows system. you can not cross compiling the application for Linux or MacOS X on a Windows system.

For Linux, please use the tools below:

Intel C++ Compiler Professional Edition for Linux

Intel VTune Analyzer for Linux 

Intel Thread Checker for Linux

For MacOS X, we currently have only the following:

Intel C++ Compiler Professional Edition for MacOS X

Please visit http://software.intel.com/en-us/articles/intel-software-evaluation-center/ for more information.

A: Yes if the code does not use "Attribute" or "CLR". 
The Intel Parallel Studio only supports native or unmanaged C/C++ program.

A: No.
Please see this article http://software.intel.com/sites/products/collateral/studio/Amplifier_VTune_Comparison.pdf for detail.

A: Yes, the Intel Parallel Studio can be used on any other brand CPUs with Windows OS. The Intel Parallel Composer has options for targeting other CPUs and the performance should be better.

 

Please see this KB for detail - http://software.intel.com/en-us/articles/performance-tools-for-software-developers-intel-compiler-options-for-sse-generation-and-processor-specific-optimizations/

A: The Intel Parallel Amplifier should not take too long like Parallel Inspector. Be sure to report problems to our Forum http://software.intel.com/en-us/forums/intel-parallel-studio/.

A: No, the Intel Parallel Studio only supports C++ native code.
If the deadlock happens in a DLL of Visual Basic, the Parallel Inspector can not find it.

A: Not right now.  A future version of the Parallel Studio will support cache miss detection.

Please use the Intel VTune Analyzer with Intel Thread Profiler for Windows.

Q:  Can the Static Analysis capability verify the correctness of say a Producer-Consumer problem with multiple threads?
A:  No, we do not have any specific checks for such a problem.

Q:  Does parallel composer run on Linux?
A:  No, the Intel® Parallel Composer is presently for Windows* only. But, you can
     use the latest "Intel® C++ Compiler Professional Edition" for Linux.

Q:  What is meant by "Compiler's interprocedural analysis capability, and can correctness of
     multiprocess applications using synchronization primitives in shared memory be checked?
A:  The inter-procedural analysis capability enables the compiler to analyze the code to determine if there is benefit in
     optimizations such as: inline function expansion, inter-procedural constant propagation, passing arguments in
     registers, dead code elimination, multi-file optimizations etc. Also, no, the correctness of multiprocess applications
     using synchronization primitives in shared memory cannot be checked.

Q:  If "parallel lint" does not report on data dependencies in my program, does it mean that I can be
     sure that my program is free of data dependencies?
A:  No. In addition, the theorem of Heodel says that this task cannot be resolved at all.

Q:  Is parallel lint a part of Compiler 11.1?
A:  Yes. In Compiler 11.1, there is a complete source checker tool in addition too.

Q:  Hello, I am sort of confused! When we talk of compiler, is it the one integrated in the Parallel Studio
     or the stand alone compiler version 11 or both?
A:  Parallel lint is available in both Intel® Parallel Composer (which is available as an individual product, and is also
     integrated as a component of Intel® Parallel Studio) and the standalone Intel® C++ Compiler Professional Edition
     product.

Q:  Are there plans to support Intel®Threading Building Blocks with Parallel lint?
A:  Presently, there is no announced plans at this time, but will update as soon as any plan for this is available.

Q:  Is Parallel Lint available for Fortran? Any plan to support Fortran if not supported right now?
A:  Yes, it is available

• Useful links:
  

  http://software.intel.com/en-us/articles/parallel-lint/

      

Q. What is the website for the Webinars?

A. Visit the webinars website https://event.on24.com/event/36/88/3/rt/1/index.html

Q. Does Intel® Parallel Studio provide any support for Microsoft Visual* Studio* 2003?

A. Microsoft* Visual Studio* 2005 and 2008 are supported. Please check: http://software.intel.com/sites/products/documentation/studio/studio/en-us/2009/start/release_notes_studio.pdf

Q. What operating systems are supported?

A. Please check system requirements here: http://software.intel.com/sites/products/documentation/studio/studio/en-us/2009/start/release_notes_studio.pdf

Q. Does code need to be compiled with the Intel® Compiler or can Microsoft Compilers be used?

A. You can use either the Intel® or the Microsoft compilers.

Q. Does code need to be compiled in any special way to enable source-code views?

A. To provide accurate performance data, the Intel(R) Parallel Amplifier requires debug information for binary files it analyzes. Generating debug information should not affect compiler optimizations but the linker may turn off some default optimizations, therefore verify that the optimization switches are enabled. If debug information does not exist, the Amplifier may not unwind the call stack correctly. Note, in some cases the finalization of results for modules without debug information can take much longer than the finalization with debug information present.

Q. Do I need to use Intel® VTune^TM Performance analyzer or Intel® Thread Checker etc. any more since I found that Intel® Parallel Studio can do what VTune analyzer always do?

A. VTune analyzer provides additional functionality. For example, VTune Event Based Sampling (the ability to track processor level events) is one such area. The Intel(R) Parallel Amplifier, an Intel(R) Parallel Studio tool, provides information on the performance of your code. Use the Parallel Amplifier to analyze the following types of performance issues in your threaded applications:

- Identify the most time-consuming (hot) functions

- Locate sections of code that do not effectively utilize available processor time

- Determine the best sections of code to optimize for sequential performance and for threaded performance

- Locate synchronization objects that affect the program performance

- Find whether, where, and why your program spends time on input/output operations

- Identify and compare the performance impact of different synchronization methods, different numbers of threads, or different algorithms

Q. Are there many overlapped functions between Intel® Parallel Studio and other threading tools?

A. There are some. Moreover, Parallel Studio is built on the latest technology (PIN) for faster analysis. Also, Parallel Inspector includes memory checking in addition to "Thread Checking". Parallel Amplifier has Statistical Call Graph for profiling your applications with low overhead to detect where time is spent in your application. See Intel® Parallel Amplifier vs. Intel® VTune^TM Analyzer Comparison.

Q. Does the analysis done by Intel® Parallel Amplifier go to the level of identifying contention on global heap (so not just locking in the user's code, but also deep inside libraries)?

A. The data collector interrupts a process, collects samples of all active instruction addresses, and reproduces a call sequence (stack) upon each sample. Intel® Parallel Amplifier can identify contention on the system libraries. If you do not have the source code for those libraries, you will see just the library name and you can walk the stack back up to the New/Malloc/etc in your code.

Q. Can the Intel® Parallel Amplifier attach to a running process?

A. Currently, this is not a supported functionality. However, a running process can be analyzed via VTune analyzer.

Q. Does Intel® Parallel Studio support Linux?

A. Currently Intel® Parallel Studio is designed for Microsoft Windows*/Microsoft Visual* Studio* only. We do have an existing line of tools, including Intel® VTune analyzer, Intel® Thread Checker, and the Intel® Compiler, which run on Linux*.

Q. Is it possible to see the specific function in source code in concurrency view?

A. The source/Assembly window displays accurate information provided that:

- Your code is compiled with the debug information and debug information is written correctly in the debug information file (or symbol file).

- The source code file exists.

If there is no correct debug information, or symbol file is unavailable, the assembly data may be incorrect. In this case, the Amplifier uses heuristics to define function boundaries in the binary module.

Q. Does Amplifier support Open MP3.0 task, Win32 API and Intel® Threading Building Block?

A. Yes these are supported. Note for Intel® Threading Building Block, the Intel® Parallel Studio analysis obtained will only be thread based (not task based).

Q. Does Intel® Parallel Studio work with the Intel® Fortran compiler?

A. Intel® Parallel Studio is designed and targeted and tested for C++ software.    The analysis is based on the binary not the source, how well it works with Fortran may vary. Please be aware that in addition to Intel Parallel Studio product, Intel offers a HPC line of products that offer full support for Fortran.  This includes the Intel® Fortran compiler of course, but also Intel® VTune Performance Analyzer and Intel® Thread Checker.  The Intel Math Kernel Library also includes full Fortran interfaces to BLAS, LAPACK, FFT and other common numerical algorithms.  Most Fortran developers use the HPC line of Intel products.

Q. Does Intel® Parallel Studio provide any support for Microsoft Visual* Studio* 2003?

A. Microsoft* Visual Studio* 2005 and 2008 are supported. Please check system requirements at: http://software.intel.com/sites/products/documentation/studio/studio/en-us/2009/start/release_notes_studio.pdf

Q. What operating systems are supported?

A. Please check requirements at: http://software.intel.com/sites/products/documentation/studio/studio/en-us/2009/start/release_notes_studio.pdf

Q. Where does the profiling information come from? Is it an Intel tool?

A. Yes, you can use Intel(R) Parallel Amplifier to find hotspots in your program/application. The Intel(R) Parallel Amplifier, an Intel(R) Parallel Studio tool, provides information on the performance of your code. Use the Parallel Amplifier to analyze the following types of performance issues in your threaded applications:

- Identify the most time-consuming (hot) functions

- Locate sections of code that do not effectively utilize available processor time

- Determine the best sections of code to optimize for sequential performance and for threaded performance

- Locate synchronization objects that affect the program performance

- Find whether, where, and why your program spends time on input/output operations

- Identify and compare the performance impact of different synchronization methods, different numbers of threads, or different algorithms

Q. How do I get the material to the previous seminars and technical sessions I missed?

A. Go to www.intel.com/go/parallel under "Related Links" on the right and click "Free, on-demand parallelism webinars".

Q. Is there any Intel software tool for parallelism under Linux platform?

A. Yes. We do have an existing line of tools, including Intel® VTune analyzer, Intel® Thread Checker, and the Intel® Compilers, which run on Linux.

Q. What is the difference between Intel® VTune^TM analyzer/Intel® Thread Checker and Intel® Parallel Studio? Or can they be used in a good combination somehow?

A. Yes. Moreover, Parallel Studio is built on the latest technology (PIN) for faster analysis. Also, Parallel Inspector includes memory checking in addition to "Thread Checking". Parallel Amplifier has Statistical Call Graph for profiling your applications with low overhead to detect where time is spent in your application. See Intel® Parallel Amplifier vs. Intel® VTune^TM Analyzer Comparison.

Q. Have you had any experience using Intel Parallel Studio with large programs (500,000 lines)? I have used VTune analyzer in the past and it was difficult to use because the size of the program I was working with was large.

A. The Intel® Parallel Studio offers a more streamlined and simplified usage model for hotspot analysis similar to VTune analyzer. The sampling methodology used is the same. This means that with big applications you have to watch for sampling overhead and the influence this has on your application sampling. You may want to consider focusing your sampling on application subsets and individual application components rather than the whole application and use a stepped approach or an approach with a smaller input data stream. All this depends a bit on the exact architecture of your application. See Intel® Parallel Amplifier vs. Intel® VTune^TM Analyzer Comparison.

Q. Is Intel® Threading Building Blocks (TBB) open source, and where may I get the source for OpenMP*?

A. Intel® Threading Building Blocks (TBB) source files can be downloaded here: http://www.threadingbuildingblocks.org/download.php. Intel's implementation of OpenMP* is not an open source project.

Q. If Intel® Parallel Advisor Lite finds the hotspot in the code, do we still have a need to use the Intel® Parallel Amplifier for finding hotspot?

A. Intel® Parallel Advisor Lite works on the serial portions of your application.  It leverages Intel® Parallel Amplifier's hot spot analysis to help identify likely areas in your serial application to experiment with parallelism - in particular, we recommend using Parallel Amplifier's "Top Down" view where one would work up the call tree to find a likely site.

If all you need are hot spots, then Parallel Advisor Lite has already found them for you by leveraging Parallel Amplifier.  However, once you have added parallelism, Parallel Amplifier can help you tune the parallelism using the Concurrency analysis to see where the threading is being used effectively, and the Locks and Waits analysis to determine if the program is wasting resources in synchronization sequences.

Q: Is the thread-to-core ratio hardwired 1:1 in Intel® Threading Building Blocks (Intel® TBB) or is it configurable?
A: The number of worker threads in Intel TBB thread pool equals the number of logical cores by default. The default number can be changed: you can specify the desired number of threads as a parameter to the constructor of Intel TBB initialization object task_scheduler_init. Please visit http://www.threadingbuildingblocks.org/documentation.php and read the related chapter in the tutorial for the complete example.

Q: What if my code contains data-dependency? Can Intel® Threading Building Blocks (Intel® TBB) detect it?
A: No, Intel TBB doesn't analyze code to detect data dependencies. Intel TBB is a library that provides generic algorithms and data structures that simplify threading and it is recommended that all data dependencies are known before applying threading. Data races arguably constitute the most commonly encountered errors in parallel code, and this type of error occurs when data dependencies are not properly handled by the programmer. Intel® Parallel Inspector is a developer oriented tool for finding data races in threaded applications. 

Q: What is the advantage of re-implementing ChangeArray(A) as a functor?
A: Most of Intel® Threading Building Blocks (Intel® TBB) algorithms take a functor object as a parameter. To take advantage of easy threading and "future proof" parallelism, which Intel TBB algorithms deliver, a developer should implement the logic of a parallel task as a functor. A less highly touted feature of Intel TBB is that the library provides excellent mechanisms to handle task-based parallelism while still emphasizing the data parallelism model. For simple loops, one may well question the advantages of using Intel TBB as opposed to other threading models. However, for more complicated loops, Intel TBB seems to provide much more flexibility than other threading models. One example of this is to consider iterating over a collection of items which is not indexed by an integer.  

Q: What do you mean by a "warmer" task describing the effectiveness of task scheduling performed by Intel® Threading Building Blocks (Intel® TBB)?
A: A warmer task is a task which is most likely to still reside in the cache. Executing "warm" tasks while they are still in the cache is more efficient than executing "cold" tasks whose data will have to be fetched into the cache first. Intel TBB task scheduler's approach to scheduling tasks favors "warm" tasks over "cold" tasks which makes scheduling highly efficient.

Q:  Just thinking about use of cache_aligned_allocator vs. scalable_allocator - does Intel® Threading Building Blocks (Intel® TBB) provide an API for obtaining any metrics about the processor caches/cache-lines etc?
A: No. That type of information can be examined using the Intel® VTune Performance Analyzer, which can monitor processor-specific events including cache misses and other cache-related activity.

Q: Your examples are for the for-loop, is it also true for while-loop? How do I parallelize non-indexed loops with Intel® Threading Building Blocks (Intel® TBB)?
A: Intel TBB implements several template classes and functions to simplify threading of non-indexed loops. For example, parallel_do (for while-loops) and pipeline (data flow pipelines). Please see the Intel TBB documentation to learn more: http://www.threadingbuildingblocks.org/documentation.php.

Q: Does Intel® Parallel Studio require a C++ compiler or is one included?
A: Intel® C++ Compiler is included in Intel Parallel Studio; it is one of the components of Intel® Parallel Composer.

Q: Which versions of Microsoft Visual Studio* are supported by Intel® Parallel Studio?
A: Microsoft Visual Studio* 2005 and 2008.

Q: What do I gain when I compile the source code with Intel® C++ Compiler compared to Microsoft's compiler? If there is a gain, several projects are impossible to convert to Intel® Compiler, such as COM-projects using attributes. And projects using BOOST are cumbersome since I need to compile BOOST*-versions for the Intel Compiler. It would be great if Intel provided already compiled BOOST library dlls and libs?
A: That is correct. COM attributes are not supported right now. We don't provide special builds of 3^rd party libraries but it should be easy to compile them with Intel C++ Compiler. Also, binaries built with Intel C++ Compiler are fully compatible with binaries built with Microsoft's compiler so both types of binaries can be safely mixed within one application. Therefore, you should be able to link object files created with the Intel compiler and your source code with the BOOST libraries created with the Microsoft compiler.  If you have any issues compiling BOOST with Intel C++ Compiler, please let us know via a forum: http://software.intel.com/en-us/forums.

Q: I know Intel® Threading Building Blocks (Intel® TBB) works with AMD processors, will Intel® Parallel Studio?
A: Intel® Parallel Studio runs on platforms with an IA-32 or Intel® 64 architecture processor supporting the Intel® Streaming SIMD Extensions 2 (Intel® SSE2) instructions (Intel® Pentium 4 processor or later, or compatible non-Intel processor).

Q: Does Intel® Parallel Studio work under Microsoft Windows* 7 and Visual Studio* 10?
A: The first releases of Intel Parallel Studio have not been validated against Microsoft Windows* 7 and Visual Studio* 10, since neither is a released product. We will, of course, move forward closely aligned with the Microsoft roadmap and validate those platforms in future releases.

Q: Is Intel® Threading Building Blocks (Intel® TBB) aware of dynamic logical partitioning activity like 2 cores out of say 8 being pulled out during application-runtime?
A: Intel TBB does not have any dynamic mechanisms to detect such situations. The number of threads is selected during initialization of the Intel TBB task scheduler. The user either chooses how many threads will be created or allows Intel TBB to take the default (which is 1 thread per logical core). For the situation you mention, provided the logical partitioning mechanism does not interrupt normal code execution (due to some system level dependency), Intel TBB code will continue to execute with a thread pool of size determined at time of the scheduler initialization.