In addition, NAG recommends that before calling any Library routine you should read the following reference material (see Section 5):
(a) Essential Introduction
(b) Chapter Introduction
(c) Routine Document
The libraries supplied with this implementation have been compiled in a manner that facilitates the use of multiple threads.
http://www.nag.co.uk/doc/inun/cl23/l6idcl/postrelease.html
for details of any new information related to the applicability or usage of this implementation.
In this section we assume that the library and the NAG include files have been installed in the directory [INSTALL_DIR].
By default [INSTALL_DIR] (see Installer's Note (in.html)) is /opt/NAG/cll6i23dcl or /usr/local/NAG/cll6i23dcl depending on your system; however it could have been changed by the person who did the installation. To identify [INSTALL_DIR] for this installation:
icc driver.c -I[INSTALL_DIR]/include -m64 [INSTALL_DIR]/lib/libnagc_mkl.a \
-Wl,--start-group \
[INSTALL_DIR]/mkl_intel64/libmkl_intel_ilp64.a \
[INSTALL_DIR]/mkl_intel64/libmkl_intel_thread.a \
[INSTALL_DIR]/mkl_intel64/libmkl_core.a \
-Wl,--end-group \
-openmp -lpthread -lm
where driver.c is your application program.
Alternatively, you can link like this:
icc driver.c -I[INSTALL_DIR]/include -m64 -L[INSTALL_DIR]/lib -lnagc_mkl \
-L[INSTALL_DIR]/mkl_intel64 -lmkl_intel_ilp64 -lmkl_intel_thread -lmkl_core \
-openmp -lpthread -lm
if the shareable library is required.
Please note that the shareable library is fully resolved so that you
need not link against other run-time libraries
explicitly; this requires the environment
variable LD_LIBRARY_PATH to be set correctly at link time
(see below).
However, if you prefer to link to a version of the NAG C Library which does not require the use of MKL you may wish to use the self-contained libraries as follows:
icc driver.c -I[INSTALL_DIR]/include -m64 [INSTALL_DIR]/lib/libnagc_nag.a \
-lpthread -lm
or
icc driver.c -I[INSTALL_DIR]/include -m64 [INSTALL_DIR]/lib/libnagc_nag.so \
-lpthread -lm
if the shareable library is required.
In case you want to use a different compiler or indeed an earlier
version of the Intel compiler, icc, you may need to link
against the libraries provided in [INSTALL_DIR]/rtl/. For instance, to use
gcc 4.1.2 onwards, you can use one of the following commands:
To use the MKL based NAG Library with static linkage:
gcc driver.c -I[INSTALL_DIR]/include -m64 [INSTALL_DIR]/lib/libnagc_mkl.a \
-Wl,--start-group \
[INSTALL_DIR]/mkl_intel64/libmkl_intel_ilp64.a \
[INSTALL_DIR]/mkl_intel64/libmkl_intel_thread.a \
[INSTALL_DIR]/mkl_intel64/libmkl_core.a \
-Wl,--end-group \
[INSTALL_DIR]/rtl/libimf.a $[INSTALL_DIR]/rtl/libirc.a \
[INSTALL_DIR]/rtl/libsvml.a \
[INSTALL_DIR]/rtl/libiomp5.a -lpthread -lm
To use the MKL based NAG Library with shared linkage:
gcc driver.c -I[INSTALL_DIR]/include -m64 -L[INSTALL_DIR]/lib -lnagc_mkl \
-L[INSTALL_DIR]/mkl_intel64 -lmkl_intel_ilp64 -lmkl_intel_thread -lmkl_core \
-L[INSTALL_DIR]/rtl -limf -lirc -lsvml -liomp5 -lpthread -lm
To use the the self contained NAG Library with static linkage:
gcc driver.c -I[INSTALL_DIR]/include -m64 [INSTALL_DIR]/lib/libnagc_nag.a \
[INSTALL_DIR]/rtl/libimf.a $[INSTALL_DIR]/rtl/libirc.a \
[INSTALL_DIR]/rtl/libsvml.a -lpthread -lm
To use the the self contained NAG Library with shared linkage:
gcc driver.c -I[INSTALL_DIR]/include -m64 [INSTALL_DIR]/lib/libnagc_nag.so \
-L[INSTALL_DIR]/rtl -limf -lirc -lsvml -lpthread -lm
These commands can easily be enabled in the nagc_example* scripts. Please refer to the comments in the scripts for more details.
If your application has been linked with static or shareable NAG and MKL Libraries you may find that the following warning message is produced non-Intel machines (and sometimes on Intel machines) even if no calls have been made to the underlying OpenMP thread libraries.
OMP: Warning #72: KMP_AFFINITY: affinity only supported for Intel(R) processors. OMP: Warning #71: KMP_AFFINITY: affinity not supported, using "none".This is a known issue
In order to suppress these warnings the scripts nagc_example_mkl and nagc_example_shar_mkl set the environment variable KMP_AFFINITY to none.
In general the the environment variable LD_LIBRARY_PATH must be set (or extended) to allow run-time linkage, when using shareable libraries, however for this implementation, the environment variable LD_LIBRARY_PATH must be extended in any case, due to the presence of the ancillary library, libmxlin64.so.2.6.0 which is required to support the NAG Kusari Licence System.
In the C shell type:
setenv LD_LIBRARY_PATH [INSTALL_DIR]/lib:[INSTALL_DIR]/mkl_intel64to set LD_LIBRARY_PATH, or
setenv LD_LIBRARY_PATH [INSTALL_DIR]/lib:[INSTALL_DIR]/mkl_intel64:
${LD_LIBRARY_PATH}
to extend LD_LIBRARY_PATH if you already have it set.
In the Bourne shell, type:
LD_LIBRARY_PATH=[INSTALL_DIR]/lib:[INSTALL_DIR]/mkl_intel64 export LD_LIBRARY_PATHto set LD_LIBRARY_PATH, or
LD_LIBRARY_PATH=[INSTALL_DIR]/lib:[INSTALL_DIR]/mkl_intel64:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH
to extend LD_LIBRARY_PATH if you already have it set.
Note that you may also need to set LD_LIBRARY_PATH to point at other things such as compiler run-time libraries, for example if you are using a newer (or an older) version of the Intel compiler, icc or a different compiler such as gcc. The runtime libraries of the compiler used to build this implementation are provided in [INSTALL_DIR]/rtl.
The distributed example results are those obtained with the static library libnagc_mkl.a (using the MKL BLAS and LAPACK routines).
Note that the example material has been adapted, if necessary, from that published in the Library Manual, so that programs are suitable for execution with this implementation with no further changes. The distributed example programs should be used in preference to the versions in the Library Manual wherever possible.
The directory [INSTALL_DIR]/scripts contains four scripts nagc_example_mkl, nagc_example_shar_mkl, nagc_example and nagc_example_shar.
The example programs are most easily accessed by one of the commands
Each command will provide you with a copy of an example program (and its data and options file, if any), compile the program and link it with the appropriate libraries (showing you the compile command so that you can recompile your own version of the program). Finally, the executable program will be run with appropriate arguments specifying data, options and results files as needed.
The example program concerned is specified by the argument to the command, e.g.
nagc_example_mkl e04uccwill copy the example program and its data and options files (e04ucce.c, e04ucce.d and e04ucce.opt) into the current directory, compile the program and run it to produce the example program results in the file e04ucce.r.
dggevx dsbev dsbevx dstedc zggev zggevx zhpr zhbev zhbevx zhpsv zspsv zsptrf zhpsv zhpsvx zhptrf zspsvx zsptrf
Functions in these Chapters will give error messages if called with illegal or unsafe arguments.
General details are given in the Library Manual, but parameter limits which are implementation specific are given below:
s07aac F_1 = 1.0e+13
F_2 = 1.0e-14
s10aac E_1 = 1.8715e+1
s10abc E_1 = 7.080e+2
s10acc E_1 = 7.080e+2
s13aac x_hi = 7.083e+2
s13acc x_hi = 1.0e+16
s13adc x_hi = 1.0e+17
s14aac fail.code = NE_REAL_ARG_GT if x > 1.70e+2
fail.code = NE_REAL_ARG_LT if x < -1.70e+2
fail.code = NE_REAL_ARG_TOO_SMALL if abs(x) < 2.23e-308
s14abc fail.code = NE_REAL_ARG_GT if x > x_big = 2.55e+305
s15adc x_hi = 2.65e+1
s15aec x_hi = 2.65e+1
s15afc underflow trap was necessary
s15agc fail.code = NW_HI if x >= 2.53e+307
fail.code = NW_REAL if 4.74e+7 <= x < 2.53e+307
fail.code = NW_NEG if x < -2.66e+1
s17acc fail.code = NE_REAL_ARG_GT if x > 1.0e+16
s17adc fail.code = NE_REAL_ARG_GT if x > 1.0e+16
fail.code = NE_REAL_ARG_TOO_SMALL if 0 < x <= 2.23e-308
s17aec fail.code = NE_REAL_ARG_GT if abs(x) > 1.0e+16
s17afc fail.code = NE_REAL_ARG_GT if abs(x) > 1.0e+16
s17agc fail.code = NE_REAL_ARG_GT if x > 1.038e+2
fail.code = NE_REAL_ARG_LT if x < -5.7e+10
s17ahc fail.code = NE_REAL_ARG_GT if x > 1.041e+2
fail.code = NE_REAL_ARG_LT if x < -5.7e+10
s17ajc fail.code = NE_REAL_ARG_GT if x > 1.041e+2
fail.code = NE_REAL_ARG_LT if x < -1.9e+9
s17akc fail.code = NE_REAL_ARG_GT if x > 1.041e+2
fail.code = NE_REAL_ARG_LT if x < -1.9e+9
s17dcc fail.code = NE_OVERFLOW_LIKELY if abs(z) < 3.92223e-305
fail.code = NW_SOME_PRECISION_LOSS if abs(z) or fnu+n-1 > 3.27679e+4
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) or fnu+n-1 > 1.07374e+9
s17dec fail.code = NE_OVERFLOW_LIKELY if Im(z) > 7.00921e+2
fail.code = NW_SOME_PRECISION_LOSS if abs(z) or fnu+n-1 > 3.27679e+4
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) or fnu+n-1 > 1.07374e+9
s17dgc fail.code = NW_SOME_PRECISION_LOSS if abs(z) > 1.02399e+3
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) > 1.04857e+6
s17dhc fail.code = NW_SOME_PRECISION_LOSS if abs(z) > 1.02399e+3
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) > 1.04857e+6
s17dlc fail.code = NE_OVERFLOW_LIKELY if abs(z) < 3.92223e-305
fail.code = NW_SOME_PRECISION_LOSS if abs(z) or fnu+n-1 > 3.27679e+4
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) or fnu+n-1 > 1.07374e+9
s18adc fail.code = NE_REAL_ARG_TOO_SMALL if 0 < x <= 2.23e-308
s18aec fail.code = NE_REAL_ARG_GT if abs(x) > 7.116e+2
s18afc fail.code = NE_REAL_ARG_GT if abs(x) > 7.116e+2
s18dcc fail.code = NE_OVERFLOW_LIKELY if abs(z) < 3.92223e-305
fail.code = NW_SOME_PRECISION_LOSS if abs(z) or fnu+n-1 > 3.27679e+4
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) or fnu+n-1 > 1.07374e+9
s18dec fail.code = NE_OVERFLOW_LIKELY if Re(z) > 7.00921e+2
fail.code = NW_SOME_PRECISION_LOSS if abs(z) or fnu+n-1 > 3.27679e+4
fail.code = NE_TOTAL_PRECISION_LOSS if abs(z) or fnu+n-1 > 1.07374e+9
s19aac fail.code = NE_REAL_ARG_GT if abs(x) >= 5.04818e+1
s19abc fail.code = NE_REAL_ARG_GT if abs(x) >= 5.04818e+1
s19acc fail.code = NE_REAL_ARG_GT if x > 9.9726e+2
s19adc fail.code = NE_REAL_ARG_GT if x > 9.9726e+2
s21bcc fail.code = NE_REAL_ARG_LT if an argument < 1.583e-205
fail.code = NE_REAL_ARG_GE if an argument >= 3.765e+202
s21bdc fail.code = NE_REAL_ARG_LT if an argument < 2.813e-103
fail.code = NE_REAL_ARG_GT if an argument >= 1.407e+102
The values of the mathematical constants are provided in the header file nagx01.h:
X01AAC (pi) = 3.1415926535897932 X01ABC (gamma) = 0.5772156649015328
The values of the machine constants are provided in the header file nagx02.h:
The basic parameters of the model
X02BHC = 2 X02BJC = 53 X02BKC = -1021 X02BLC = 1024 X02DJC = Nag_TRUEDerived parameters of the floating-point arithmetic
X02AJC = 1.11022302462516e-16 X02AKC = 2.22507385850721e-308 X02ALC = 1.79769313486231e+308 X02AMC = 2.22507385850721e-308 X02ANC = 2.22507385850721e-308Parameters of other aspects of the computing environment
X02AHC = 1.42724769270596e+45 X02BBC = 9223372036854775807 X02BEC = 15 X02DAC = Nag_TRUE
The Library Manual is available as part of the installation or via download from the NAG website. The most up-to-date version of the documentation is accessible via the NAG website at http://www.nag.co.uk/numeric/CL/CLdocumentation.asp.
The Library Manual is supplied in the following formats:
The following main index files have been provided for these formats:
nagdoc_cl23/pdf/FRONTMATTER/manconts.pdf nagdoc_cl23/html/FRONTMATTER/manconts.htmlUse your web browser to navigate from here. For convenience, a master index file containing links to the above files has been provided at
nagdoc_cl23/index.html
Advice on viewing and navigating the formats available can be found in the Online Documentation document.
In addition the following are provided:
The NAG Response Centres are available for general enquiries from all users and also for technical queries from sites with an annually licensed product or support service.
The Response Centres are open during office hours, but contact is possible by fax, email and phone (answering machine) at all times.
When contacting a Response Centre, it helps us deal with your enquiry quickly if you can quote your NAG site reference or account number and NAG product code (in this case CLL6I23DCL).
The NAG websites provide information about implementation availability, descriptions of products, downloadable software, product documentation and technical reports. The NAG websites can be accessed at the following URLs:
NAG Ltd Wilkinson House Jordan Hill Road OXFORD OX2 8DR NAG Ltd Response Centre United Kingdom email: support@nag.co.uk Tel: +44 (0)1865 511245 Tel: +44 (0)1865 311744 Fax: +44 (0)1865 310139 Fax: +44 (0)1865 310139 NAG Inc 801 Warrenville Road Suite 185 Lisle, IL 60532-4332 NAG Inc Response Center USA email: support@nag.com Tel: +1 630 971 2337 Tel: +1 630 971 2337 Fax: +1 630 971 2706 Fax: +1 630 971 2706 Nihon NAG KK Hatchobori Frontier Building 2F 4-9-9 Hatchobori Chuo-ku Tokyo 104-0032 Nihon NAG Response Centre Japan email: support@nag-j.co.jp Tel: +81 3 5542 6311 Tel: +81 3 5542 6311 Fax: +81 3 5542 6312 Fax: +81 3 5542 6312 NAG Taiwan Branch Office 5F.-5, No.36, Sec.3 Minsheng E. Rd. Taipei City 10480 NAG Taiwan Response Centre Taiwan email: support@nag-gc.com Tel: +886 2 25093288 Tel: +886 2 25093288 Fax: +886 2 25091798 Fax: +886 2 25091798