Linking Tools and Options

This topic describes how to use the Intel® linking tools, xild (Linux* OS and OS X*) or xilink (Windows* OS).

The Intel linking tools behave differently on different platforms. The following sections summarizes the primary differences between the linking behaviors.

Linux OS and OS X Linking Behavior Summary
The linking tool invokes the compiler to perform IPO if objects containing IR (intermediate representation) are found. (These are mock objects.) It invokes GNU `ld` to link the application. The command-line syntax for `xild` is the same as that of the GNU linker: `xild [<options>] <normal command-line>` where: `[<options>]`: (optional) one or more options supported only by `xild`. `<normal command-line>`: linker command line containing a set of valid arguments for `ld`. To create `app` using IPO, use the option -o`filename` as shown in the following example: `xild -qipo-fas -oapp a.o b.o c.o` The linking tool calls the compiler to perform IPO for objects containing IR and creates a new list of object(s) to be linked. The linker then calls `ld` to link the object files that are specified in the new list and produce the application with the name specified by the -o option. The linker supports the -ipo[`n`] and -ipo-separate options. To display a list of the supported link options from xild, use the following command: `$ xild -qhelp`

Linux OS and OS X Linking Behavior Summary

The linking tool invokes the compiler to perform IPO if objects containing IR (intermediate representation) are found. (These are mock objects.) It invokes GNU ld to link the application.

The command-line syntax for xild is the same as that of the GNU linker:

xild [<options>] <normal command-line>

where:

[<options>]: (optional) one or more options supported only by xild.
<normal command-line>: linker command line containing a set of valid arguments for ld.

To create app using IPO, use the option -ofilename as shown in the following example:

xild -qipo-fas -oapp a.o b.o c.o

The linking tool calls the compiler to perform IPO for objects containing IR and creates a new list of object(s) to be linked. The linker then calls ld to link the object files that are specified in the new list and produce the application with the name specified by the -o option. The linker supports the -ipo[n] and -ipo-separate options.

To display a list of the supported link options from xild, use the following command:

$ xild -qhelp

Windows OS Linking Behavior Summary
The linking tool invokes the Intel compiler to perform multi-file IPO if objects containing IR (intermediate representation) is found. These are mock objects. It invokes Microsoft* link.exe to link the application. The command-line syntax for the Intel® linker is the same as that of the Microsoft linker: `xilink [<options>] <normal command-line>` where: `[<options>]`: (optional) one or more options supported only by `xilink`. `<normal command-line>`: linker command line containing a set of valid arguments for the Microsoft linker. To place the multifile IPO executable in ipo_file.exe, use the linker option /out:`filename`; for example: `xilink -qipo-fas /out:ipo_file.exe a.obj b.obj c.obj` The linker calls the compiler to perform IPO for objects containing `IR` and creates a new list of object(s) to be linked. The linker calls Microsoft link.exe to link the object files that are specified in the new list and produce the application with the name specified by the /out:`filename` linker option. To display a list of support link options from xilink, use the following command: `>> xilink /qhelp` `xilink.exe`accepts all the options of `link.exe` and will pass them on to `link.exe` at the final linking stage.

Windows OS Linking Behavior Summary

The linking tool invokes the Intel compiler to perform multi-file IPO if objects containing IR (intermediate representation) is found. These are mock objects. It invokes Microsoft* link.exe to link the application.

The command-line syntax for the Intel® linker is the same as that of the Microsoft linker:

xilink [<options>] <normal command-line>

where:

[<options>]: (optional) one or more options supported only by xilink.
<normal command-line>: linker command line containing a set of valid arguments for the Microsoft linker.

To place the multifile IPO executable in ipo_file.exe, use the linker option /out:filename; for example:

xilink -qipo-fas /out:ipo_file.exe a.obj b.obj c.obj

The linker calls the compiler to perform IPO for objects containing IR and creates a new list of object(s) to be linked. The linker calls Microsoft link.exe to link the object files that are specified in the new list and produce the application with the name specified by the /out:filename linker option.

To display a list of support link options from xilink, use the following command:

>> xilink /qhelp

xilink.exeaccepts all the options of link.exe and will pass them on to link.exe at the final linking stage.

Using the Linking Tools

You must use the Intel linking tools to link your application if the following conditions apply:

Your source files were compiled with multifile IPO enabled. Multi-file IPO is enabled by specifying compiler option -ipo (Linux OS and OS X) or /Qipo (Windows OS) .
You normally would invoke either the GNU linker (ld) or the Microsoft linker (link.exe) to link your application.

Controlling the Display of Diagnostics

The following table provides information on the -qdiag linking option.

Linking Tools Option

Description

-qdiag-[type]=[diag-list]

Controls the display of diagnostic information.

The type is an action to perform on diagnostics. Possible values are:

enable	Enables a diagnostic message or a group of messages.
disable	Disables a diagnostic message or a group of messages.

The diag-list is a diagnostic group or ID value. Possible values are:

thread	Specifies diagnostic messages that help in thread-enabling a program.
vec	Specifies diagnostic messages issued by the vectorizer.
par	Specifies diagnostic messages issued by the auto-parallelizer (parallel optimizer).
openmp	Specifies diagnostic messages issued by the OpenMP* parallelizer.
warn	Specifies diagnostic messages that have a "warning" severity level.
error	Specifies diagnostic messages that have an "error" severity level.
remark	Specifies diagnostic messages that are remarks or comments.
cpu-dispatch	Specifies the CPU dispatch remarks for diagnostic messages. These remarks are enabled by default.
id[,id,...]	Specifies the ID number of one or more messages. If you specify more than one message number, they must be separated by commas. There can be no intervening white space between each "id".
tag[,tag,...]	Specifies the mnemonic name of one or more messages. If you specify more than one mnemonic name, they must be separated by commas. There can be no intervening white space between each "tag".

The diagnostic messages generated can be affected by certain options, such as /arch or /Qx (Windows OS) or -m or -x (Linux OS and OS X).

Note that in the above option, you can specify an underscore (_) instead of a dash (-).