Jump to main content
MPLAB® XC32 C/C++ Compiler User's Guide for PIC32M MCUs
MPLAB® XC32 C/C++ Compiler User's Guide for PIC32M MCUs
  1. Home
  2. 3 How To's
  3. 3.5 Understanding the Compilation Process
  4. 3.5.11 How Can I Tell How Big a Function Is?
  • Notice to Development Tools Customers
  • 1 Preface
  • 2 Compiler Overview
  • 3 How To's
    • 3.1 Installing and Activating the Compiler
    • 3.2 Invoking the Compiler
    • 3.3 Writing Source Code
    • 3.4 Getting My Application To Do What I Want
    • 3.5 Understanding the Compilation Process
      • 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.5.20 How Do I Stop My Project's Checksum From Changing?
    • 3.6 Fixing Code That Does Not Work
  • 4 XC32 Toolchain and MPLAB X IDE
  • 5 Command-line Driver
  • 6 ANSI C Standard Issues
  • 7 Device-Related Features
  • 8 Code Coverage
  • 9 Supported Data Types and Variables
  • 10 Memory Allocation and Access
  • 11 Floating-point Support
  • 12 Fixed-Point Arithmetic Support
  • 13 Operators and Statements
  • 14 Register Usage
  • 15 Stack
  • 16 Functions
  • 17 Interrupts
  • 18 Main, Runtime Start-up and Reset
  • 19 Library Routines
  • 20 Mixing C/C++ and Assembly Language
  • 21 Optimizations
  • 22 Preprocessing
  • 23 Linking Programs
  • 24 Embedded Compiler Compatibility Mode
  • 25 Common C Interface
  • 26 C Implementation-Defined Behavior
  • 27 C++ Implementation-Defined Behavior
  • 28 Deprecated Features
  • 29 Built-In Functions
  • 30 Built-In DSP Functions
  • 31 PIC32 DSP Library
  • 32 PIC32 Debug-Support Library
  • 33 DSP Wrapper Functions
  • 34 ASCII Character Set
  • 35 Document Revision History
  • The Microchip Website
  • Product Change Notification Service
  • Customer Support
  • Product Identification System
  • Microchip Devices Code Protection Feature
  • Legal Notice
  • Trademarks
  • Quality Management System
  • Worldwide Sales and Service

3.5.11 How Can I Tell How Big a Function Is?

This size of a function (the amount of assembly code generated for that function) can be determined from the assembly list file. See 3.5.10 How Do I Know What Code the Compiler Is Producing? for more on creating an assembly listing file.

The online versions of the documents are provided as a courtesy. Verify all content and data in the device’s PDF documentation found on the device product page.

Microchip Facebook
Microchip LinkedIn
Microchip Twitter
Microchip YouTube
Microchip Instagram
Microchip Weibo
Microchip Blog
Contact |
Legal |
Privacy Policy |
Cookies |
Careers

Stay on the leading edge with our blog

MicroSolutions

© Copyright 1998-2022 Microchip Technology Inc. All rights reserved.