Chronos Ouroboros

Sure thing. [Here's a modified version of the BasicCompute unit test](https://github.com/doom2fan/veldrid/commit/f5bf2149912a30fb0a852f00e8697ae4d3d1a23d) that does this.

[Here's a hacked up test for this issue](https://github.com/Doom2fan/veldrid/commit/e0b6d519cb75cdc46bfc67283db1d5502740cece). It's hacked onto NeoDemo. This is what it should look like: 

This is, indeed, caused by incorrectly using the first mip level as the source of all the other mip levels. I've made a PR (#349) that fixes this and issue...

This can be closed now that #349 was merged.

> But to solve this issue for Rack 2, I think I'll make newly compiled plugins dynamically link to Rack's libstdc++. I've tested this and it seems to build plugins...

> [@Doom2fan](https://github.com/Doom2fan) Can you post your plugin source code that fails to load when the `-static-libstdc++` flag is removed? https://github.com/Doom2fan/OuroborosModules/tree/MakeOnly This is the plugin, using a plain Makefile. Adding ```...

Curiously, I can't reproduce it with local builds anymore, only the toolchain ones... The original report here is for the toolchain, though, so maybe reproducing it locally was a fluke....

If I'm understanding the [GCC libstdc++ documentation](https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html) correctly, the issue might be one of backwards incompatibility. From what I understood, programs and libraries built against an earlier version of libstdc++...

> This sounds like the exact same issue as this one: [VCVRack/rack-plugin-toolchain#41](https://github.com/VCVRack/rack-plugin-toolchain/issues/41) > > has the SDK and toolchain been changed to static? If so then yes we will need...

That's indeed what I'm saying. If you instruct CMake to generate Makefiles and search in the build directory's files, you can see that `-static-libstdc++` is missing, and `-march=nehalem` is only...