Checklist for ILP32-to-LP64 post-migration activities

After migrating a program, test the code and confirm that its behavior is the same under LP64 as it was under ILP32. Use the following checklist to test the code. If you see any difference, debug the code and use the pre-migration checklist again.

1. Verify that all output produced is contained in the 4-byte range.

   If this is not possible, then any other application using this data needs to be ported to LP64 or, at least, be made 8-byte-aware.

2. Verify that any user-provided process containing the wchar_t type definition did not produce unexpected results.

   UNIX wchar_t data types are typically defined as four bytes under both 32-bit and 64-bit environments. The size difference applies to the ILP32 model, not the LP64 model. The new environment was an opportunity to increase the size for future development. Because wchar_t is a type definition, user-provided methods are a likely problem area. A carefully-written application should not require changes.