Intel Software Network articles feed http://software.intel.com/en-us/articles/dpd-general/tips-and-techniques/ en-us Intel® Software Development Products – Events Events

Upcoming Events

Come and see Intel® Software Development Products in action at events!

Participate in technology and product demonstrations, training talks and sessions, network with our team on the floor, and learn more about our latest and greatest products!

Microsoft Professional Developers Conference
November 17-19, 2009
Los Angeles, California
http://microsoftpdc.com/

Supercomputing '09
November 14-20, 2009
Portland, Oregon
http://sc09.supercomputing.org/

 Events
]]> http://software.intel.com/en-us/articles/intel-software-development-products-events Wed, 21 Oct 2009 09:22:54 -0700 http://software.intel.com/en-us/articles/intel-software-development-products-events#comments http://software.intel.com/en-us/articles/intel-software-development-products-events Software Products General What are the Intel Password Guidelines
The password must be at least eight characters long, and can contain
letters, numbers, and punctuation.
It must not exceed fourteen (14) characters.
It must contain at least one alpha character [a-z; A-Z], one numeric [0-9]
and one special character [`! @$%^&*()-_=+[];:'",<.>/?].
It cannot contain spaces.
The password cannot be the same as any of your previous eight (8) passwords.

It cannot contain your login id.
It may not contain any of the following special characters: Asterisk (*)
Comma (,) Backslash ( /) Forward Slash (\).
It must not:

Be a name (your own, family members, pets, or famous people)
Be your social security number, driver's license number, passport number or
some other identification number.
Be repeating numbers, letters or characters (111111, aaaaaa, !!!!!!)
Be a number or character combinations that are next to each other on the
keyboard (123456, asdfgh)
Be a dictionary word of any language
Begin with an exclamation point (!) or question mark (?)
Have the same first three characters.
]]> http://software.intel.com/en-us/articles/what-are-the-intel-password-guidelines Mon, 19 Oct 2009 14:10:55 -0700 http://software.intel.com/en-us/articles/what-are-the-intel-password-guidelines#comments http://software.intel.com/en-us/articles/what-are-the-intel-password-guidelines Software Products General Intel Software Network communities Intel® Software Development Products Registration Center Knowledge Base Intel Software Network communities How to find Host ID for Floating licenses
Identifying the Host Name and Host ID
The host name and host ID are system-level identifiers on supported platforms that
are used in the license file to identify the node on which you plan to install the Intel
License Manager for FLEXlm* and license file. To enable you to obtain a counted
license, these unique values must be available when you register your product. For
node-locked licenses, you will also need the host name and host id of the node from
which your applications will run, if different from the node for the Intel License
Manager for FLEXlm*. Follow these directions to obtain the host name and host id for
each supported platform:

Microsoft Windows*
1. From the Start menu, click Run...
2. Type cmd in the Open: field, then click OK.
3. Type ipconfig /all at the command prompt, and press Enter.
In the resulting output, host name is the value that corresponds to Host Name, and
host id is the value that corresponds to Physical Address.

For example, if the output of ipconfig /all included the following:
Host Name . . . . . . . : mycomputer
. . .
Physical Address . . . . : 00-06-29-CF-74-AA
then host name is mycomputer and the host ID is 00-06-29-CF-74-AA.

Linux*
1. Run the hostname command to display the host name.
2. Run the command /sbin/ifconfig eth0 to display the hardware address.
For example, if the /sbin/ifconfig eth0 command returns
HWaddr 00:D0:B7:A8:80:AA, then the host ID is 00:D0:B7:A8:80:AA.
It is strongly recommended that users run the lmhostid utility to obtain the hostid
value required to generate the counted licenses. The lmhostid utility can be found in
the install location to which Intel License Manager for FLEXlm* is installed.

Mac OS* X on Intel® Architecture
1. Run the hostname command to display the host name.
2. Run the command /sbin/ifconfig en0 ether to display the hardware address.
The following is an example of an address that could be returned by this command:
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:13:20:60:23:4f
It is strongly recommended that users run the lmhostid utility to obtain the hostid
value required to generate the counted licenses. The lmhostid utility is installed to
the same location as the Intel License Manager for FLEXlm*.

]]> http://software.intel.com/en-us/articles/how-to-find-host-id-for-floating-licenses Thu, 13 Aug 2009 09:15:55 -0700 http://software.intel.com/en-us/articles/how-to-find-host-id-for-floating-licenses#comments http://software.intel.com/en-us/articles/how-to-find-host-id-for-floating-licenses Software Products General Intel® Compilers Intel® License Manager for FLEXlm* Knowledge Base Intel® Software Development Products Registration Center Knowledge Base Intel® Thread Checker for Linux* - General Installation Information

Page Contents:


What software must already be installed?
Before installing Intel® Thread Checker onto Microsoft Windows*, you must have the VTune™ Performance Analyzer v7.2 already installed, as Intel® Thread Checker is a plug-in to the VTune™ environment. Visit the Intel® Threading Tools Web site to obtain VTune Performance Analyzer and/or Intel Thread Checker.

On Microsoft Windows systems, you must also have the following already installed:

  • Microsoft Visual* C++ v6.0, or higher
  • Intel® Compilers are required for source instrumentation or OpenMP* analysis.
  • Microsoft* Internet Explorer v6.0, or higher
  • Adobe* Reader*

To use the Linux* Remote Data Collector (Remote Agent), you must also install Intel Thread Checker on a Microsoft Windows system.


Installing a New Version Over an Already Installed Version
To install a new version of Intel Thread Checker, you must first uninstall the currently installed version.

Note: Before removing the current version from Windows, you might want to save your projects using File » Pack and Go menu in the VTune environment.

To remove the currently installed version from Windows*, go to Start » Control Panel » Add or Remove Programs » Intel® Thread Checker.

To remove the currently installed version from Linux, run uninstall32.sh or uninstall64.sh, which is typically found in the /opt/intel/itt directory.


General Installation Tips for Linux*

  • To use the Linux Remote Data Collector (Remote Agent), you must also install Intel Thread Checker on a Microsoft Windows system.
  • The Remote Data Collector (RDC) .tar file for Linux is included with the Windows* installation package.
  • If you use ftp* to transfer the RDC .tar file to a Linux system, be sure to use a binary transfer.
  • If you are also using the Intel Compilers on your Linux system, you should install Intel Compilers before installing Intel Thread Checker.
    • If you update your Intel Compilers after installing Thread Checker, re-run the Thread Checker install script after updating the Intel Compilers.
    • Installation includes a script tcvars.sh (and tcvars.csh), typically in the /opt/intel/itt/tcheck/bin/32 or /opt/intel/itt/tcheck/bin/64 directory. Use the source tcvars.sh command to setup the shell environment for source instrumentation with the Intel® Compiler.
    • After installation, see the file tcheckFAQ.htm, typically found in the /opt/intel/itt directory, for important overview and usage information.
    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-general-installation-information Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-general-installation-information#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-general-installation-information Software Products General Intel® Thread Checker for Windows* Knowledge Base     Intel® Thread Checker for Linux* - Tips and Techniques

    Page Contents:


    I don't have source code. Can I use Intel® Thread Checker?
    Yes. For example: You are using an executable file from another vendor, so you don't have source code to it. But you are interested in diagnostics about a library (.dll or .so file) that is loaded by the vendor's executable file. You may not even have source code for the library that gets loaded. You can still use Thread Checker to see if any threading diagnostics are detected.Of course, if you really want to correct threading issues, you'll need source code.


    Collecting Thread Checker Diagnostics Outside of the VTune™ Environment
    To collect diagnostics outside of the VTune™ environment, follow this process:
    1. Compile your software using an Intel® Compiler and the /Qtcheck (on Microsoft Windows*) or -tcheck (on Linux*) switch. This option enables source instrumentation.

    2. Start your software as usual from the Windows*, DOS* or Linux* environment. For example, use Windows Explorer* to browse to your executable file and double-click on that file name.

    3. Run your software until it terminates normally. Don't forget to reduce your workload. Also because your software is instrumented, expect that it will run slower than usual.

    4. Exit (quit) your software, and a Thread Checker results ("*.thr") file is written to the working folder. If you are running on a Linux* system, transfer the .thr results file back to a Microsoft Windows* system (with Thread Checker installed) for viewing.

    5. To view the results file with Windows* Explorer, simply double-click the file. Alternatively you can start the VTune environment and open it with the File » Open File ... (NOT Open Project...) dialog. Important: Don't forget to set the file type to *.thr when using this dialog.
    Keep in mind that when collecting data outside of the VTune environment, only software that has been source instrumented will be analyzed by Thread Checker. Therefore, threading errors in the not instrumented softwa re may be missed. To ensure that all run-time code is instrumented, you must run from within the VTune environment or Microsoft .NET* Developer Environment.

    Note: Many third-party libraries, such as MFC* (Microsoft Foundation Class*) libraries, create and use threads. Therefore, software that uses MFC should always be run from within the VTune environment or Microsoft .NET* Developer Environment


    Analyze Multiple Processes or Executables
    Intel® Thread Checker only supports one process (executable) when run from within either the VTune™ environment or Microsoft .NET* Developer Environment. Furthermore, Thread Checker only supports finding diagnostics within one process; that is it will not produce diagnostics for synchronization objects shared between processes. However if your software launches another process, Thread Checker can still be used to find threading diagnostics within either process. To use Thread Checker for either process, use source instrumentation and run your software outside of the VTune™ environment.
    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-tips-and-techniques Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-tips-and-techniques#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-tips-and-techniques Software Products General Intel® Thread Checker for Windows* Knowledge Base     Intel® Thread Checker for Linux* - Compiler settings for Linux* OpenMP* applications when using Thread Checker

    Recommended Intel® Compiler Settings for Linux* OpenMP* Applications When Using the Intel® Thread Checker

    Get the best results from Intel® Thread Checker by using the following command to compile your Linux* OpenMP* applications:

    icc file.c -openmp [-tcheck] -O0 -g
    Switch Purpose
    -openmp
    (required)    		 Tells the compiler to process the OpenMP* pragmas.
    -tcheck
    (optional)    		 Enables thread count independent (TCI) analysis mode instead of thread count dependent (TCD) analysis mode on OpenMP* applications.
    -O0
    (recommended)

    Allows Intel® Thread Checker to more easily associate errors to source lines.

    Intel® Thread Checker can also analyze optimized binaries, but it is difficult for Intel® Thread Checker to pinpoint the source code location causing a problem in optimized assembly that does not have specific source lines.
    -g
    (highly recommended)

    Creates symbols for the binary. Intel® Thread Checker uses the symbols to associate addresses to source lines.

    Note: For binaries compiled without -g (no symbols), Intel® Thread Checker instruments using API Imports. Intel® Thread Checker cannot find all threading errors within a binary that is instrumented with API Imports. The Default of API Imports instrumentation on a particular file can be changed to Full Image via advanced settings in Intel® Thread Checker, but the result is that you will not see the source code that caused the problem, only the assembly.

    Note: Intel® Thread Checker requires the dynamic versions of the following libraries:

    • OpenMP* Runtime Library (libguide.so or libiomp5.so)
    • Posix* Thread Library (libpthread.so)
    • C Runtime Library (libc.so)

    Linking to any of the following static libraries causes problems with Intel® Thread Checker:

    • OpenMP* Runtime Library (libguide.a or libiomp5.a)
    • Posix* Thread Libra ry (libpthread.a)
    • C Runtime Library (libc.a)

    The switch -static is not compatible with Intel® Thread Checker, as it links the static version of these libraries.

    Related Documentation

    • Using Intel® Thread Checker on OpenMP* Applications Compiled with the GNU* GCC Compiler

    Confirmed On:

    • Intel® C/C++ Compiler 10.1 for Linux*
    • Intel® Fortran Compiler 10.1 for Linux*
    • Intel® Thread Checker 3.1 for Linux*
    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-compiler-settings-for-linux-openmp-applications-when-using-thread-checker Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-compiler-settings-for-linux-openmp-applications-when-using-thread-checker#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-linux-compiler-settings-for-linux-openmp-applications-when-using-thread-checker Software Products General Intel® Thread Checker for Linux* Knowledge Base     Intel® Thread Checker - Tips for Analyzing Long Diagnostic Lists

    This document provides the best known method for dealing with long diagnostic lists in Intel® Thread Checker.

    iconTips for Analyzing Long Diagnostic Lists [BKM.PDF]
    Size: 2586113 bytes
    Date: 03/14/03 02:38 PM

    Note: PDF Files require Adobe Acrobat* Reader†



    † This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.

    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-tips-for-analyzing-long-diagnostic-lists Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-tips-for-analyzing-long-diagnostic-lists#comments http://software.intel.com/en-us/articles/intel-thread-checker-tips-for-analyzing-long-diagnostic-lists Software Products General Intel® Thread Checker for Windows* Knowledge Base     Intel® Thread Checker - Threading Methodology [PDF]

    This document introduces threading concepts and provides a methodology for threading serial applications and for tuning threaded applications for performance using the Intel® Threading Tools.

    icon Threading Methodology: Practices & Principles [PDF]
    File Name: methodology.pdf
    Size: 1,684,645 bytes
    Date: 10/30/04

    Note: PDF Files require Adobe Acrobat* Reader†



    † This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.

    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-threading-methodology-pdf Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-threading-methodology-pdf#comments http://software.intel.com/en-us/articles/intel-thread-checker-threading-methodology-pdf Software Products General Intel® Thread Checker for Windows* Knowledge Base     Intel® Thread Checker for Windows* - Product Overview

    Intel® Thread Checker is a tool that locates software threading bugs, such as data races, stalls, and deadlocks. Thread Checker monitors your software's execution to detect hard-to-find and impossible-to-find intermittent errors whether or not they actually occurred during execution.

    Thread Checker uses instrumentation, which occurs automatically at run-time within the VTune environment or Microsoft .NET* Developer Environment, or can be performed beforehand with the Intel® C++ or Fortran Compilers.

    When your software has finished executing, a diagnostic list of potential threading errors will be displayed. You can drill down to the line of source code where each diagnostics occurred, look at the call stack, and review variable definitions and context.

    For more information on this product, including how to purchase or get a free evaluation copy, please visit the Intel® Threading Tools web site.

    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-product-overview Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-product-overview#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-product-overview Software Products General Intel® Thread Checker for Windows* Knowledge Base     Intel® Thread Checker for Windows* - Preparing Your Software: Building or Making Source Code

    Page Contents:


    Tips on Preparing Microsoft Windows* Code for Intel® Thread Checker
    The following are general tips for preparing Windows* source code for Intel® Thread Checker. Build (make) your source with the following switches:

    • Be sure to build thread-safe by compiling with the /MD, /MDd, /MT or /MTd switch. This will use the thread-safe run-time libraries.

      Note: The default for Microsoft* and Intel® Compilers is the /ML or /MLd switch and this does not use thread-safe libraries.

    • Generate symbols by compiling with the /Zi, /ZI or /Z7 switches and link with the /DEBUG switch. This will enable Thread Checker to specify source code information (file name and line number) with its diagnostics.

    • Compile without optimization using the /Od switch. Just like when using a debugger, this will enable Thread Checker source code information (especially line numbers) to be accurate. Moreover, turning on compiler optimizations is usually not beneficial for code run under Intel Thread Checker.

    • Executable software must be built so that it contains a relocation section that allows for relocation in memory. Relocation is required for instrumentation. Most dynamic-link library (.dll) files can be relocated by default; however by default, most executable (.exe) files cannot be relocated. So always link with the /FIXED:NO switch to allow for relocation.

      Tip: Instead of changing your project's settings, set the (system) environment variable LINK to the value /FIXED:NO and re-link your code to add a relocation section.

    • To reduce executable (.dll or .exe) code size, link with the /INCREMENTAL:NO switch.

    Intel® Thread Checker Run-Time Warnings for Microsoft Windows* Applications
    If you get the warning "modules were created without base relocations" when you run Intel® Thread Checker activity in the VTune™ environment or Microsoft .NET* Development Environment, your code probably doesn't contain a relocation section. Link with the /FIXED:NO switch to add a relocation section.

    I don't have source code. Can I use Intel® Thread Checker?
    Yes -- But on Microsoft Windows*, do not expect to get any threading diagnostics for the application (.exe) file itself b ecause typically on Windows the executable does not have a relocation section.

    An example of using Thread Checker without source code might be if you are using an application file from another vendor, so you don't have source code for the for the application. But you are interested in diagnostics about a dynamic or shared library file that is loaded by the vendor's .application. You may not even have source code for the library that gets loaded. You can still use Thread Checker to see if any threading diagnostics are detected. Of course, if you really want to correct threading issues, you'll need source code.

    ]]>     http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-preparing-your-software-building-or-making-source-code Fri, 19 Sep 2008 00:00:00 -0700 http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-preparing-your-software-building-or-making-source-code#comments http://software.intel.com/en-us/articles/intel-thread-checker-for-windows-preparing-your-software-building-or-making-source-code Software Products General Intel® Thread Checker for Windows* Knowledge Base