<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fortran on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/fortran/</link>
    <description>Recent content in Fortran on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/fortran/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fortran in 2026: LFortran vs Flang vs gfortran — Which Compiler Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-13-fortran-toolchain-lfortran-flang-gfortran-fpm-comparison/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-13-fortran-toolchain-lfortran-flang-gfortran-fpm-comparison/</guid>
      <description>&lt;p&gt;Fortran is 69 years old, and it is still the language that produces the weather forecast you read this morning, the finite-element stress numbers behind every bridge inspection, and a large share of the world&amp;rsquo;s climate simulation output. The language never lost its job. What did change — quietly, over the last three years — is the toolchain around it. In 2026 you no longer have exactly one realistic compiler choice, and that is genuinely new.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
