Search results

This document provides Fortran interface blocks for MASS scalar and vector functions.

This document provides C/C++ prototypes for MASS scalar and vector functions.

This document provides performance data for the MASS scalar and vector libraries for AIX, in comparison with the standard system math libraries.

Installing Update 4, 5 and 6 of Red Hat Enterprise Linux AS 3 can cause problems building applications with VisualAge C++ Version 6.0 for Linux or XL C/C++ Advanced Edition Version 7.0 for Linux. For example, building the C++ version of a Hello World program results in the errors shown below: $ cat HelloWorld.cpp #include <iostream> using namespace std; int main() { cout << "Hello World!" << endl; return 0; } $ xlC -c HelloWorld.cpp "/usr/include/c++/3.2.3/limits", line 1732.16:

IBM has standardized on the C++ Standard Library, including the Standard Template Library (STL) and other features of the ISO C++ 1998 Standard, and removed support for the IBM Open Class Library from the latest releases of the C++ compiler products on the z/OS, AIX and iSeries platforms. This change in IBM’s direction has been communicated to customers. Application owners and customers whose applications depend on the IBM Open Class Library will need to migrate away from using the IBM Open Class Lib

Is there an alternative to the operating system's memory allocation for small objects that may offer better performance?

How do I use the -qcheck compiler option to check for array bounds problems in VisualAge C++ V6 for AIX? And how do I check static array bounds in XL C/C++ V7.0 for AIX during compile time?

In the interest of speed, certain MASS vector functions may produce slightly different results for a given input value, depending on its position in the vector, the vector length, and nearby elements of the input vector. In most applications, these inconsistencies will not have any significant impact.

When I compile my source files in 64-bit mode by specifying the -q64 compiler option, the compiler doesn't seem to be able to find many of the header files. This problem does not happen when I am not compiling in 64-bit mode.

The following test case prints the result of the subtraction of two single-precision floating point numbers. The result is incorrect. What is the problem? /* t.c */ #include <stdio.h> int main() { float f1 = 520.02; float f2 = 520.04; float result = f1 - f2; printf("result=%f, expected -0.02\n", result); } $ xlc t.c && a.out result=-0.019958, expected -0.02