Pierre Kestener pkestene

In general, check the crt/host_config.h file to find out which versions are supported. Sometimes it is possible to hack the requirements there to get some newer versions working, too :)

Thrust version can be found in $CUDA_ROOT/include/thrust/version.h.

Download Archives: https://developer.nvidia.com/cuda-toolkit-archive

Release notes for CUDA Toolkit (CTK):

latest: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html
archive: https://docs.nvidia.com/cuda/archive/

Effective Modern CMake

Getting Started

For a brief user-level introduction to CMake, watch C++ Weekly, Episode 78, Intro to CMake by Jason Turner. LLVM’s CMake Primer provides a good high-level introduction to the CMake syntax. Go read it now.

After that, watch Mathieu Ropert’s CppCon 2017 talk Using Modern CMake Patterns to Enforce a Good Modular Design (slides). It provides a thorough explanation of what modern CMake is and why it is so much better than “old school” CMake. The modular design ideas in this talk are based on the book [Large-Scale C++ Software Design](https://www.amazon.de/Large-Scale-Soft

What is the Strict Aliasing Rule and Why do we care?

(OR Type Punning, Undefined Behavior and Alignment, Oh My!)

What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.

In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.

Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th

Computational Fluid Dynamics (in graphics mostly)

Disclaimer: I have no professional education in Compulational Fluid Dynamics, these are various notes on what I found/learned when trying to learn a bit on the topic. Some of the notes lack sources as I wrote them up later often just remembering some StackExchange answer. Some things I might have misinterpreted.

Computational Fluid Dynamics (in graphics mostly)
General / Overview
- Overarching resources
General Concepts & Keywords

Since version 2.23, git-blame has a feature to ignore certain commits. This feature is useful to ignore large formatting or apparently unimportant changes.

How to use

Create a revisions list file. The file name is usually .git-blame-ignore-revs
Set the file as a default ignore file for blame by git config blame.ignoreRevsFile .git-blame-ignore-revs

The file format is described in git-fsck's man: https://git-scm.com/docs/git-fsck#Documentation/git-fsck.txt-fsckskipList

	#include <algorithm>
	#include <array>
	#include <cassert>
	#include <experimental/string_view>
	#include <functional>
	#include <initializer_list>
	#include <iterator>
	#include <utility>

	/**
	* A simple theme for reveal.js presentations, derived from serif.css
	* It's in the spirit of the Metropolis theme for beamer https://github.com/matze/mtheme
	*
	* This theme is Copyright (C) 2016 Vince Hodges, http://sourdoughlabs.com - it is MIT licensed.
	*/

	@import url('https://fonts.googleapis.com/css?family=Fira+Sans');

	.reveal a {

	#include <random>
	#include <algorithm>
	#include <iostream>
	#include <cmath>

	// header file for the hc API
	#include <hc.hpp>

	#define N (1024 * 500)

	# Sexy Bash Prompt, inspired by "Extravagant Zsh Prompt"
	# Screenshot: http://cloud.gf3.ca/M5rG
	# A big thanks to \amethyst on Freenode

	if [[ $COLORTERM = gnome-* && $TERM = xterm ]] && infocmp gnome-256color >/dev/null 2>&1; then export TERM=gnome-256color
	elif [[ $TERM != dumb ]] && infocmp xterm-256color >/dev/null 2>&1; then export TERM=xterm-256color
	fi

	if tput setaf 1 &> /dev/null; then
	if [[ $(tput colors) -ge 256 ]] 2>/dev/null; then