# Using Intel's valarray Implementation

Intel's valarray implementation allows you to declare huge arrays for parallel processing. Improved implementation of valarray is tied up with calling the IPP libraries that are part of Intel® Integrated Performance Primitives (Intel® IPP).

This content is specific to C++; it does not apply to DPC++.

## Using valarray in Source Code

To use valarrays in your source code, include the valarray header file, `<valarray>`. The `<valarray>` header file is located in the path <installdir>/perf_header.

The example code below shows a valarray addition operation (+) specialized through use of Intel's implementation of valarray:

    #include <valarray>
    void test( )
    {
    	std::valarray<float> vi(N), va(N);
    	…
    	vi = vi + va;  //array addition
    	…
    }

### Note

To use the static merged library containing all CPU-specific optimized versions of the library code, you need to call the ippStaticInit function first, before any IPP calls. This ensures automatic dispatch to the appropriate version of the library code for Intel® processor and the generic version of the library code for non-Intel processors at runtime. If you do not call ippStaticInit first, the merged library will use the generic instance of the code. If you are using the dynamic version of the libraries, you do not need to call ippStaticInit.

## Compiling valarray Source Code

To compile your valarray source code, the compiler option, `/Quse-intel-optimized-headers` (for Windows*) or `-use-intel-optimized-headers` (for Linux*), is used to include the required valarray header file and all the necessary IPP library files.

The following examples illustrate how to compile and link a program to include the Intel valarray replacement header file and link with the Intel® IPP libraries. Refer to the Intel® IPP documentation for details.

In the following examples, "merged" libraries refers to using a static library that contains all the CPU-specific variants of the library code.

## Windows* OS examples:

The following command line performs a one-step compilation for a system based on IA-32 architecture, running Windows OS:

    icx /Quse-intel-optimized-headers source.cpp

The following command lines perform separate compile and link steps for a system based on IA-32 architecture, running Windows OS:

DLL (dynamic):

    icx /Quse-intel-optimized-headers /c source.cpp

    icx source.obj /Quse-intel-optimized-headers

Merged (static):

    icx /Quse-intel-optimized-headers /Qipp-link:static /c source.cpp
    icx source.obj /Quse-intel-optimized-headers /Qipp-link:static

## Linux* OS examples:

The following command line performs a one-step compilation for a system based on Intel® 64 architecture, running Linux OS:

    icpx -use-intel-optimized-headers source.cpp

The following command lines perform separate compile and link steps for a system based on Intel® 64 architecture, running Linux OS:

so (dynamic):

    icpx -use-intel-optimized-headers -c source.cpp

    icpx source.o -use-intel-optimized-headers -shared-intel

Merged (static):

    icpx -use-intel-optimized-headers -c source.cpp

    icpx source.o -use-intel-optimized-headers

Product and Performance Information
Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex. Notice revision #20201201

Parent topic: Intel's valarray Implementation