Did your application build without errors?

After the program is successfully built, make sure you test it for runtime errors. Runtime errors are usually related to your program logic in this phase. You should also run the test programs you defined during planning to verify that the output of your application is the one you expected.

Potential issues and solutions

Dependencies (libraries, runtimes, packages and proper versions

• Check all dependencies, especially closed-source, that are not contained in the enterprise Linux distributions or new, emerging technologies, such as a new language
• Check OSPAT to see if dependent packages have been ported to POWER

Assembler code, including hand-coded vector (SSE) instructions

• Intel Assembler does not run on Power
• If you decide to install the SDK for Linux on Power, it includes helpful porting tools such as the Migration Advisor, which recognizes some common x86 assembler instructions and recommends Power equivalents

Platform-specific compiler flags and intrinsics

• POWER-specific differences from x86
• Often, generic compiler intrinsics can be used in place of platform-specific
• For your C/C++ application the SDK for Linux on Power includes a tool called the Build Advisor, which scans your project build output and recommends “best practices” you can implement for improved results. It looks for compilers (type and version), optimization levels, processor-specific optimization, and other compiler and linker flags.