<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GCC on Marcus Folkesson</title>
    <link>https://www.marcusfolkesson.se/tags/gcc/</link>
    <description>Recent content in GCC on Marcus Folkesson</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Mar 2026 12:00:34 +0100</lastBuildDate>
    <atom:link href="https://www.marcusfolkesson.se/tags/gcc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracing function calls in C with -finstrument-functions</title>
      <link>https://www.marcusfolkesson.se/blog/tracing-function-calls-in-c/</link>
      <pubDate>Thu, 19 Mar 2026 12:00:34 +0100</pubDate>
      <guid>https://www.marcusfolkesson.se/blog/tracing-function-calls-in-c/</guid>
      <description>Tracing Function Calls in C with -finstrument-functions Some time ago, I wrote a blog post about mutex guards in the Linux kernel [1]. It uses a cool feature in GCC which allows you to cleanup resources when they go out of scope. I have a few of such GCC features that I use every now and then, which often show itself handy in the most unexpected way. -finstrument-functions is one of those.</description>
    </item>
  </channel>
</rss>
