The following sections describe ways of using Oracle Developer Studio Performance Library routines without making source code changes or recompiling.
Many applications use one or more of the base Netlib libraries, such as LAPACK or BLAS. Because Oracle Developer Studio Performance Library maintains the same interfaces and functionality of these libraries, base Netlib routines can be replaced with Oracle Developer Studio Performance Library routines. Application performance is increased, because Oracle Developer Studio Performance Library routines can be faster than the corresponding Netlib routines or similar routines provided by other vendors.
Many commercial math libraries are built around a core of generic BLAS and LAPACK routines. When an application has a dependency on proprietary interfaces in another library that prevents the library from being completely replaced, the BLAS and LAPACK routines used in that library can be replaced with the Oracle Developer Studio Performance Library BLAS and LAPACK routines. Because replacing the core routines does not require any code changes, the proprietary library features can still be used, and the other routines in the library can remain unchanged.
Some libraries that do not directly use Oracle Developer Studio Performance Library routines can be modified by using automatic code restructuring tools that replace existing code with Oracle Developer Studio Performance Library code. For example, a source- to- source conversion tool can replace existing BLAS code structures with calls to the Oracle Developer Studio Performance Library BLAS routines. These conversion tools can also recognize many user written matrix multiplications and replace them with calls to the matrix multiplication subroutine in Oracle Developer Studio Performance Library.