TNS/E Native Application Conversion Guide

Contents

TNS/E Native Application Conversion Guide—529659-003

2. Developing a Conversion Strategy

Native Architecture Features (continued)

Signals Facility 1-16

DLLs 1-17

Native Mode Conversion Considerations 1-18

KMSF 1-19

Benefits of Native Mode 1-21

Constraints of Native Mode 1-22

2. Developing a Conversion Strategy

Determining Which Programs to Convert 2-1

Preparing Programs for Conversion 2-2

Planning System Resources 2-2

Maintaining Common Source Code for TNS and TNS/E Native Compilers 2-3

Adjusting for Increased DCT Limits 2-4

Determining Optimization Levels 2-5

Determining Data Alignment 2-6

Converting Programs With Misaligned Data 2-7

Tuning the Performance of Native Programs 2-8

Detecting Compatibility Traps 2-8

Eliminating Compatibility Traps 2-8

3. C and C++ Conversion Tasks

Using the Native C and C++ Compilers 3-2

Converting Code to Use 32-Bit Pointers and Integers 3-3

Using IEEE Floating Point Format 3-4

Replacing Obsolete External Function Declarations 3-5

Replacing Obsolete Keywords 3-5

Changing Use of _cc_status for Return Values 3-5

Replacing Calls to Obsolete C Library Supplementary Functions 3-7

Replacing Calls to Obsolete C Library Guardian Alternate-Model I/O Functions 3-8

Checking Calls to Changed C Library Functions 3-10

Functions Having Different Behavior 3-10

Using the setjmp() and longjmp() Functions 3-11

Using the semctl() Function 3-11

Changing Programs That Use Guardian and OSS Environment Interoperability 3-12

Changing Code That Relies on Arithmetic Overflow Traps 3-12

Using Active Backup Programming in C 3-13

Replacing Obsolete C++ Library Operations 3-13

Using the Tools.h++ Class Library 3-13

Specifying Pragmas or Flags 3-14