4.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.

• 4.5.1 How Does Licensing Affect Features and Optimization Levels?
• 4.5.2 Why Can’t I Debug my Code after I Optimize?
• 4.5.3 How Can I Make My Code Smaller?
• 4.5.4 How Can I Reduce RAM Usage?
• 4.5.5 How Can I Make My Code Faster?
• 4.5.6 What are the Speed vs. Size Tradeoffs?
• 4.5.7 How Can I Control Where the Language Tool Places Objects in Memory?
• 4.5.8 How Can I Make My Interrupt Routine Faster?
• 4.5.9 How Big Can C Variables Be?
• 4.5.10 Which Optimizations Will Be Applied to My Code?
• 4.5.11 Which Devices are Supported by the Compiler?
• 4.5.12 How Do I Know What Code the Compiler Is Producing?
• 4.5.13 How Can I Tell How Big a Function Is?
• 4.5.14 How Do I Learn Where Variables and Functions Have Been Positioned?
• 4.5.15 How Do I Properly Reserve Memory?
• 4.5.16 How Do I Know How Much Memory Is Still Available?
• 4.5.17 Which Libraries Get Included by Default?
• 4.5.18 How Do I Create My Own Libraries?
• 4.5.19 Why Do I Get Out-of-Memory Errors When I Select a Debugger?
• 4.5.20 How Do I Stop My Project's Checksum From Changing?
• See also, 4.6.1 How Do I Find Out What a Warning or Error Message Means?
• See also, 4.2.7 How Do I Build Libraries?
• See also, 4.2.9 What is Different About an MPLAB® X IDE Debug Build?
• See also, 4.3.5.1 How Do I Stop A Function From Being Removed?