| //////////////////////////////// | |
| // NBHS - Non-blocking hashset | |
| //////////////////////////////// | |
| // You wanna intern lots of things on lots of cores? this is for you. It's | |
| // inspired by Cliff's non-blocking hashmap. | |
| // | |
| // To use it, you'll need to define NBHS_FN and then include the header: | |
| // | |
| // #define NBHS_FN(n) XXX_hs_ ## n | |
| // #include <nbhs.h> |
Example of how to capture CPU counters with ETW on Windows, perf on Linux or kperf on Apple.
Using ETW needs somewhat recently updated Windows 10 or 11. Not sure about exact version.
Currently tested on:
| // We do a little too much trolling... | |
| // | |
| // Ever wanted to pretend divisions by zero just didn't happen? here you go... | |
| // this is memes, don't try to make this work with C because the optimizer will | |
| // fight you on it. You can apply it to your own language if you really wanted. | |
| #include <stdint.h> | |
| #include <stdio.h> | |
| #define WIN32_LEAN_AND_MEAN | |
| #include <windows.h> |
I use Obsidian git on PC, and this workaround (since the plugin doesn't support mobile) to seamlessly* sync my notes to and from my phone. Using these instructions you create an automation for pulling every time you open Obsidian, and pushing every time you close it.
* you can still get merge conflicts...
termux-setup-storage, give it permissions.
A spin-off from the mainline Minimal D3D11 series, adding two-lane instanced rendering. As before: An uncluttered Direct3D 11 setup & basic rendering primer / API familiarizer. Complete, runnable Windows application contained in a single function and laid out in a linear, step-by-step fashion. No modern C++ / OOP / obscuring cruft.
The main difference here is that the hollow cube itself is rendered using instancing (which saves a lot of vertices compared to the original, so geometry data is now small enough to be included in the source without being too much in the way), but also all trigonometry and matrix math is moved to the vertex shader, simplifying the main code (and not needing math.h).
In this case, each instance is mere
The 4 C's of good technical communication:
Concision not only saves the audience time, it cuts out distracting verbiage and helps avoid burying key information in a sea of boiler plate.
Audiences very often revisit sources, and concision makes it easier to relocate particular bits of information.
Smaller pieces are easier to rearrange, and so in practice, the more concise, the more authors are likely to work out an ideal structure.
| #ifndef defer | |
| struct defer_dummy {}; | |
| template <class F> struct deferrer { F f; ~deferrer() { f(); } }; | |
| template <class F> deferrer<F> operator*(defer_dummy, F f) { return {f}; } | |
| #define DEFER_(LINE) zz_defer##LINE | |
| #define DEFER(LINE) DEFER_(LINE) | |
| #define defer auto DEFER(__LINE__) = defer_dummy{} *[&]() | |
| #endif // defer |
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
I'm assuming you are familiar with symbol servers - you might not have one set up yourself for your own projects, but you probably use Microsoft's public symbol server for downloading symbols for system DLLs.
For your own projects it might be useful to set up a symbol server - I won't go into how you do that here since it's well documented elsewhere, but basically you just set up a folder somewhere - say X:\symbols\ or \servername\symbols or even http://servername.foo/symbols/ which has a defined tree structure:
symbols/
symbols/mymodule.pdb/
symbols/mymodule.pdb/123456789012345678901234567890122/