<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Simd on Matt Bolitho</title><link>https://mattbolitho.github.io/tags/simd/</link><description>Recent content in Simd on Matt Bolitho</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><copyright>Matt Bolitho</copyright><lastBuildDate>Thu, 08 May 2025 19:00:00 +0000</lastBuildDate><atom:link href="https://mattbolitho.github.io/tags/simd/index.xml" rel="self" type="application/rss+xml"/><item><title>Skipping hardware instruction dependent tests in C#</title><link>https://mattbolitho.github.io/posts/skipping-hardware-instruction-dependent-tests-in-csharp/</link><pubDate>Thu, 08 May 2025 19:00:00 +0000</pubDate><guid>https://mattbolitho.github.io/posts/skipping-hardware-instruction-dependent-tests-in-csharp/</guid><description>When writing tests for a project that uses hardware intrinsics, we face the problem of ensuring that we only run tests that the host hardware supports. I recently ran into this issue for a personal project in C#, and wanted to write a post about it. There is nothing hugely complicated here, but it does allow us to explore hardware intrinsics, standard library API design, and practical testing advice in a single post.</description></item></channel></rss>