<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pimpl on icyveins7's blog</title><link>https://icyveins7.github.io/tags/pimpl/</link><description>Recent content in Pimpl on icyveins7's blog</description><generator>Hugo</generator><language>en-us</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Wed, 13 Aug 2025 20:00:00 +0800</lastBuildDate><atom:link href="https://icyveins7.github.io/tags/pimpl/index.xml" rel="self" type="application/rss+xml"/><item><title>Some tips for integrating small bits of CUDA code into larger codebases</title><link>https://icyveins7.github.io/posts/2025/08/some-tips-for-integrating-small-bits-of-cuda-code-into-larger-codebases/</link><pubDate>Wed, 13 Aug 2025 20:00:00 +0800</pubDate><guid>https://icyveins7.github.io/posts/2025/08/some-tips-for-integrating-small-bits-of-cuda-code-into-larger-codebases/</guid><description>&lt;blockquote&gt;&#10;&lt;p&gt;Some lessons from general C++ come in handy here..&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;In some recent work I integrated some CUDA code I developed into a larger existing codebase, written for the CPU. Essentially, my module(s) would accelerate and replace some existing functionality, but was only a small cog in the machine.&lt;/p&gt;&#10;&lt;p&gt;This is likely applicable to many others, so hopefully the lessons I document here will be concisely useful to those who chance upon this post.&lt;/p&gt;</description></item></channel></rss>