# Code Size Optimization: GCC Compiler Flags | Interrupt

**URL:** https://community.memfault.com/t/code-size-optimization-gcc-compiler-flags-interrupt/73
**Category:** Blog
**Created:** [August 21, 2019, 5:49am UTC](https://community.memfault.com/t/code-size-optimization-gcc-compiler-flags-interrupt/73 "2019-08-21T05:49:41Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![discobot](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.memfault.com/discobot/32/1_2.png) [@discobot](https://community.memfault.com/u/discobot)
#### Post date: [August 21, 2019, 5:49am UTC](https://community.memfault.com/t/code-size-optimization-gcc-compiler-flags-interrupt/73/1 "2019-08-21T05:49:41Z")

</div>

This is the second post in our [Firmware Code Size Optimization](https://interrupt.memfault.com/blog/tag/fw-code-size) series. [Last time](https://interrupt.memfault.com/best-firmware-size-tools), we talked about measuring code size as a precondition to improving it. Now we’ll leap from planning into action!

* * *
This is a companion discussion topic for the original entry at [https://interrupt.memfault.com/blog/code-size-optimization-gcc-flags](https://interrupt.memfault.com/blog/code-size-optimization-gcc-flags)