1<?xml version="1.0" encoding="UTF-8"?> 2<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 3 <channel> 4 <title>Pigweed Blog</title> 5 <link>https://pigweed.dev/docs/blog/</link> 6 <description> 7 An informal blog where Pigweed teammates, contributors, and users can 8 share ideas and projects related to Pigweed. 9 </description> 10 <language>en-us</language> 11 <pubDate>Mon, 7 Oct 2024 08:00:00 -0700</pubDate> 12 <atom:link href="https://pigweed.dev/rss.xml" rel="self" type="application/rss+xml"/> 13 <item> 14 <title>C++20 coroutines without heap allocation</title> 15 <link>https://pigweed.dev/docs/blog/05-coroutines.html</link> 16 <description> 17 This blog post describes how you can use C++20 coroutines to create 18 embedded-friendly async code without writing manual state machines or 19 callbacks. 20 </description> 21 <pubDate>Mon, 7 Oct 2024 08:00:00 -0700</pubDate> 22 <guid>https://pigweed.dev/docs/blog/05-coroutines.html</guid> 23 </item> 24 <item> 25 <title>Fixed-point arithmetic as a replacement for soft floats</title> 26 <link>https://pigweed.dev/docs/blog/04-fixed-point.html</link> 27 <description> 28 We've observed a ~2x speed improvement in classification algorithms 29 and a small decrease in binary size using fixed-point without 30 sacrificing correctness. 31 </description> 32 <pubDate>Mon, 30 Sep 2024 13:47:00 -0700</pubDate> 33 <guid>https://pigweed.dev/docs/blog/04-fixed-point.html</guid> 34 </item> 35 <item> 36 <title>Pigweed SDK launch</title> 37 <link>https://pigweed.dev/docs/blog/03-pigweed-sdk.html</link> 38 <description> 39 The Pigweed team is excited to announce the launch of the first 40 preview release of the Pigweed SDK with official hardware support 41 for Raspberry Pi’s newest microprocessor products, the RP2350 and 42 Pico 2! 43 </description> 44 <pubDate>Thu, 8 Aug 2024 08:16:00 -0700</pubDate> 45 <guid>https://pigweed.dev/docs/blog/03-pigweed-sdk.html</guid> 46 </item> 47 <item> 48 <title>Feature flags in Bazel builds</title> 49 <link>https://pigweed.dev/docs/blog/02-bazel-feature-flags.html</link> 50 <description> 51 Let’s say you’re migrating your build system to Bazel. Your project 52 heavily relies on preprocessor defines to configure its code. In your 53 source files, you use these preprocessor variables to conditionally 54 compile some sections, via #ifdef. When building the same code for 55 different final product configurations, you want to set different 56 defines. How do you model this in Bazel? 57 </description> 58 <pubDate>Fri, 31 May 2024 15:54:00 -0700</pubDate> 59 <guid>https://pigweed.dev/docs/blog/02-bazel-feature-flags.html</guid> 60 </item> 61 <item> 62 <title>Kudzu</title> 63 <link>https://pigweed.dev/docs/blog/01-kudzu.html</link> 64 <description> 65 Pigweed's whimsical take on a development board. 66 </description> 67 <pubDate>Thu, 12 Oct 2023 15:14:00 -0700</pubDate> 68 <guid>https://pigweed.dev/docs/blog/01-kudzu.html</guid> 69 </item> 70 </channel> 71</rss> 72