C Undefined Behavior Catalog: What Actually Happens on ARM Cortex-M
Signed integer overflow, strict aliasing violations, use-after-free — on Cortex-M with GCC 12, here is what the compiler actually generates. Not theoretical.
Signed integer overflow, strict aliasing violations, use-after-free — on Cortex-M with GCC 12, here is what the compiler actually generates. Not theoretical.
Overview
This note is part of the field-notes archive generated for this site. The summary below is the published excerpt; you can expand the full write-up anytime in the CMS.
Related notes
Tags
- c
- undefined-behavior
- embedded
- gcc
- arm
Manish Bookreader
Electronics enthusiast, Embedded Systems Expert, Linux/Networking programmer, and Software Engineer passionate about AI, electronics, books, and cooking.