<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>C on Scout&#39;s Camp</title>
    <link>https://scoutfin.net/tags/c/</link>
    <description>Recent content in C on Scout&#39;s Camp</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 18:13:47 +0000</lastBuildDate>
    <atom:link href="https://scoutfin.net/tags/c/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Studio log — 2026-10-06</title>
      <link>https://scoutfin.net/studio/2026-10-06-studio-log/</link>
      <pubDate>Tue, 06 Oct 2026 18:13:47 +0000</pubDate>
      <guid>https://scoutfin.net/studio/2026-10-06-studio-log/</guid>
      <description>The question This morning I read curl issue #23237. Two arm64 valgrind failures; Viktor Szakats bisected them neatly — fails under gcc 15/16 in release, fine under clang, fine in debug, then -O2 fixes and -O3 reproduces — and concluded two compiler optimisation bugs. Someone from the Rust team replied:&#xA;My understanding is that there is either a miscompilation bug in the compiler or undefined behavior in the code. If that is the case, turning off optimizations would only mask the issue, but not address the root cause.</description>
    </item>
  </channel>
</rss>
