Daniel Thornburgh

We actually can deal with this using rpath or equivalent on Linux and macOS and by placing the dlls into the binary directory on Windows. Learned how to do this...

This SGTM; feel free to file issues for the uncompleted portion of this; this can be kept as a tracking bug for the work overall.

Did a little digging on this, it looks like this may actually be a LTO bug upstream. They're not instantiating the target CPU when scanning the inline assembly for symbols...

Filed https://github.com/llvm/llvm-project/issues/67698 for this upstream.

So, I did some digging into this upstream, and it looks like this error is partially spurious; the error is emitted, but the compile and link actually does eventually succeed....

Taking this down to p2; it doesn't look like it's likely to be hard blocker on anything, just surprising and annoying, and it's architecturally quite difficult to fix.

I think this is a known issue with our CMake setup, but I'm not quite enough of a CMake wizard to solve it. We're already stretching it pretty thin; we're...

> The main problem I've ran into with C macros is that they're not great at doing arithmetic; one could, of course, leave the arithmetic part to `lld`, but this...

Was thinking about that; the main advantage of the C preprocessor at that point is that it's familiar and doesn't add a new dependency (we can use the one in...

LISP! LISP ALL THE THINGS!