<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compiler on P01NT</title><link>https://outofsrvc.github.io/en/tags/compiler/</link><description>Recent content in Compiler on P01NT</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 13 Aug 2026 10:00:00 +0300</lastBuildDate><atom:link href="https://outofsrvc.github.io/en/tags/compiler/index.xml" rel="self" type="application/rss+xml"/><item><title>The Stages Code Goes Through</title><link>https://outofsrvc.github.io/en/cworkshop/compilation-stages/</link><pubDate>Thu, 13 Aug 2026 10:00:00 +0300</pubDate><guid>https://outofsrvc.github.io/en/cworkshop/compilation-stages/</guid><description>&lt;p>Assalamu alaikum wa rahmatullahi wa barakatuh.&lt;/p>
&lt;p>This series covers the fundamentals of the C language that matter most for &lt;strong>reverse engineering&lt;/strong>. We will not expand into every detail of the language — only into what matters when reading disassembly and analyzing binaries.&lt;/p>
&lt;h2 id="the-stages-c-code-goes-through">The Stages C Code Goes Through&lt;/h2>
&lt;p>We start with the &lt;strong>source code&lt;/strong> — the &lt;code>.c&lt;/code> file containing what we wrote. This code passes through four stages before it executes, and understanding them is extremely important:&lt;/p></description></item></channel></rss>