3.5 Understanding the Compilation Process

This section tells you how to find out what the compiler did during the build process, how it encoded output code, where it placed objects, etc. It also discusses the features that are supported by the compiler.

• 3.5.1 What's the Difference Between the Free and PRO Modes?
• 3.5.2 How Can I Make My Code Smaller?
• 3.5.3 How Can I Reduce RAM Usage?
• 3.5.4 How Can I Make My Code Faster?
• 3.5.5 How Does the Compiler Place Everything in Memory?
• 3.5.6 How Can I Make My Interrupt Routine Faster?
• 3.5.7 How Big Can C Variables Be?
• 3.5.8 What Optimizations Will Be Applied to My Code?
• 3.5.9 What Devices are Supported by the Compiler?
• 3.5.10 How Do I Know What Code the Compiler Is Producing?
• 3.5.11 How Can I Tell How Big a Function Is?
• 3.5.12 How Do I Know What Resources Are Being Used by Each Function?
• 3.5.13 How Do I Find Out Where Variables and Functions Have Been Positioned?
• 3.5.14 Why Are Some Objects Positioned Into Memory That I Reserved?
• 3.5.15 How Do I Know How Much Memory Is Still Available?
• 3.5.16 How Do I Use Library Files in My Project?
• 3.5.17 How Do I Customize the C Runtime Startup Code?
• 3.5.18 What Optimizations Are Employed by the Compiler?
• 3.5.19 Why Do I Get Out-of-Memory Errors When I Select a Debugger?
• 3.6.1 How Do I Set Up Warning/Error Messages?
• 3.6.2 How Do I Find the Code that Caused Compiler Errors or Warnings in My Program?
• 3.6.3 How Can I Stop Spurious Warnings From Being Produced?
• 3.6.4 Why Can’t I Even Blink an LED?
• 3.6.5 What Can Cause Corrupted Variables and Code Failure When Using Interrupts?
• 3.2.6 How Do I Build Libraries?
• 3.2.9 What is Different About an MPLAB X IDE Debug Build?
• 3.3.5.2 How Do I Stop An Unused Function Being Removed?
• 3.5.16 How Do I Use Library Files in My Project?
• 3.5.17 How Do I Customize the C Runtime Startup Code?
• 3.5.18 What Optimizations Are Employed by the Compiler?
• 3.5.19 Why Do I Get Out-of-Memory Errors When I Select a Debugger?