Welcome to the CodeWarrior Profiler User Guide. Profiler is a code analysis tool designed to help you make your code more efficient.

The introduction includes the following sections:

• Read the Release Notes!-where to go for critical, last-second details
• What's New in This Release-new features since the previous release
• CodeWarrior and Its Documentation-a general description of the CodeWarrior architecture and documentation
• What's in This Manual-a description of the contents of this manual
• Where to Go from Here-recommendations for further reading

Read the Release Notes!

Before you use CodeWarrior Profiler, you should read the release notes. They contain important last-minute information about new features, bug fixes, and incompatibilities that may not be included in the documentation.

The release notes directory is always included as part of a standard CodeWarrior installation. The release notes directory is also located at the top level of the CodeWarrior CD.

What's New in This Release

MW Profiler is Carbon compliant and thus requires the CarbonLib from Apple to run. A version of CarbonLib is available on the CodeWarrior CD.

CodeWarrior and Its Documentation

CodeWarrior is a multi-host, multi-language, multi-target development environment. What does that mean?

Multiple hosts

CodeWarrior runs on several different operating systems, including Windows and Mac OS. The features, human interface, and operation of CodeWarrior are very similar on all hosts.

Multiple languages

You can use CodeWarrior to program in several languages, including C/C++, and Java. Third-party compilers provide support for other languages, such as Fortran. Which languages are available to you depend upon the target for which you are developing software.

Multiple targets

You can use CodeWarrior to write software for several different chips or operating systems. CodeWarrior products support programming for a variety of embedded processors and real-time operating systems, the Java Virtual Machine, and desktop operating systems such as Windows, Mac OS.

Most features of CodeWarrior apply regardless of your preferred host, language, or target. General features of CodeWarrior are described in the IDE User Guide .

For a complete understanding of CodeWarrior, you must refer to both the general documentation and the documentation that is specific to your particular target.

While the profiling process is general, each target has its own unique features. This manual describes both the general profiling process and the unique features involved in profiling code for specific targets.

What's in This Manual

The CodeWarrior Profiler is actually a system consisting of three components: the profiler libraries, the calls you add to your code, and the MW Profiler application you use to view results. The Profiler system works with C, C++, and Pascal code.

This manual often refers to the CodeWarrior profiler system as "CodeWarrior profiler," or simply as "the profiler." This manual will specifically refer to the MW Profiler application as "MW Profiler."

Table 1.1 lists every chapter in this manual, and describes the information contained in each. See "CodeWarrior and Its Documentation" for a discussion of how these chapters relate to other CodeWarrior documentation.

Contents of chapters:

Chapter	Description
Introduction	this chapter
Getting Started	system requirements, installation instructions, and background information
Using Profiler	a "how to" guide to profiling your code
Viewing Results	a user's guide to displaying profiling results with MW Profiler
Profiling Mac OS Code	information about profiling Mac OS code, including a tutorial
Troubleshooting	common problems and their answers
Profiler Reference	a reference to the libraries, compiler directives, and function calls you use to control the CodeWarrior profiler at compile time

Where to Go from Here

All the manuals mentioned here are available as part of the CodeWarrior documentation included with your product.

If you're new to CodeWarrior Profiler:

• If you are unfamiliar with what a profiler is, read "What Is a Profiler?." This section discusses different approaches to profiling code, and why profiling is so useful.
• Read "Using Profiler" and "Viewing Results." These chapters introduce you to the three components of the CodeWarrior profiler system: the profiler libraries, the calls you add to your code, and the MW Profiler application you use to view results.

If you're experienced with CodeWarrior Profiler:

• For details about profiling Mac OS code, read "Profiling Mac OS Code."
• If you are experiencing problems using any part of the CodeWarrior profiler system, read "Troubleshooting."
• For technical details on the CodeWarrior profiler system, including the libraries, API, and other issues, see "Profiler Reference."
• For reference on menu items in the MW Profiler application, use "Profiler Menu Reference" as your starting point.

For everyone:

• For general information about the CodeWarrior IDE and debugger, see the IDE User Guide .
• For information specific to the C/C++ front-end compiler, see the C Compilers Reference.
• For information on Metrowerks' standard C/C++ libraries, see the MSL C Reference and the MSL C++ Reference.

For general information on profiling Mac OS code:

• Read "Optimizing PowerPC Programs," Apple Directions, Nov. 95, p. 17.
• Read "Balance of Power," develop, Issues 18 (p. 55) and 19 (p. 17)
• Read "PowerPC Compatibility and Performance Issues," Tech Note PT38.
• Read "Taking Extreme Advantage of PowerPC," MacTech Magazine, Eric Traut, April 95
• Read "Preparing Your Code for Future PowerPC Processors," Apple Directions, May 95, p. 14.

There is a complete index at the back of this manual.