Preface

This document describes how to use KAP C software on OpenVMS Alpha systems.

Intended Audience

This document is a guide for KAP users working with C on OpenVMS Alpha systems.

Structure of This Document

This document is organized into the following chapters and appendixes:

• Chapter 1 provides an overview of KAP C software.

• Chapter 2 presents general information on how to run KAP on OpenVMS Alpha systems. The sections describing how to compile and run programs with KAP are specific to single-processor systems.

• Chapter 3 presents information on how to compile and run programs with KAP on symmetric multiprocessor systems.

• Chapter 4 describes the command- line qualifiers used at run time to alter KAP default activities, such as causing KAP to set optimization levels or enable/disable classes of transformations.

• Chapter 5 describes KAP assertions and directives. Assertions provide KAP with additional information about the input program that would normally be unknown at compile time. Directives are in-line instructions to KAP and function in many ways like command-line qualifiers.

• Chapter 6 contains more information about inlining, Interprocedural Analysis (IPA), and the KAP command-line qualifiers and directives that control them.

• Chapter 7 offers examples of KAP transformations from ordinary C code into more efficient forms. Users just becoming acquainted with KAP may want to begin by browsing in this chapter.

• Chapter 8 describes the KAP optional listing file and messages to users.

• Appendix A describes data dependence analysis and explains how KAP uses this information to determine if a given loop can be optimized.

Associated Documents

This document is part of the KAP document set that also includes:

• KAP C for OpenVMS Alpha Installation Guide

• KAP C for OpenVMS Alpha Quick Reference

• KAP C for OpenVMS Alpha Cover Letter

Conventions

The following conventions are used in this guide:

Convention	Description
< >	Angle brackets denote command input you replace with the appropriate value.
( )	Parentheses containing a single command value denote the default value. For example, (/optimize=5) denotes 5 is the default value. Parentheses containing hyphenated value ranges denote that you choose a value from the range.
[ ]	Square brackets indicate optional syntax. For example: #pragma _KAP [no]inline [(name)]
italic type	Italic type indicates complete titles of manuals and keywords.

1