<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>compilers on Ciência Programada</title>
    <link>https://cienciaprogramada.com/tags/compilers/</link>
    <description>Recent content in compilers on Ciência Programada</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>contato[@]cienciaprogramada.com.br (Francisco Bustamante)</managingEditor>
    <webMaster>contato[@]cienciaprogramada.com.br (Francisco Bustamante)</webMaster>
    <copyright>© 2026 Francisco Bustamante</copyright>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cienciaprogramada.com/tags/compilers/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Python and Compilers: A Didactic Bridge to the CPython Pipeline</title>
      <link>https://cienciaprogramada.com/2026/05/python-bytecode-compilers/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <author>contato[@]cienciaprogramada.com.br (Francisco Bustamante)</author>
      <guid>https://cienciaprogramada.com/2026/05/python-bytecode-compilers/</guid>
      <description>Python does not run your code line by line: first, CPython compiles it to bytecode. With the tokenize, ast, compile, and dis modules, we follow a simple expression from tokens to syntax tree to bytecode, right in the interpreter.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://cienciaprogramada.com/2026/05/python-bytecode-compilers/featured_0067.jpg" />
    </item>
    
    <item>
      <title>Program Execution: From Source Code to Machine Code</title>
      <link>https://cienciaprogramada.com/2026/05/program-execution/</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <author>contato[@]cienciaprogramada.com.br (Francisco Bustamante)</author>
      <guid>https://cienciaprogramada.com/2026/05/program-execution/</guid>
      <description>You write a line of code, and the processor only understands bits. We follow the translation: the two-pass assembler, the compiler phases, linking and loading. Along the way, GCC cuts twelve instructions down to two with -O2, and we see where Python and Java sit between compiling and interpreting.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://cienciaprogramada.com/2026/05/program-execution/featured_0066.jpg" />
    </item>
    
  </channel>
</rss>
