Gareth Francis

The issue here is that the crash handler uses some fiddly assembly tricks, and is only written for x86. As you're on an ARM board building with the same settings...

Yes, atomic as part of LIBRARIES is good. Perhaps this is a suitable example: https://github.com/llvm-mirror/llvm/blob/master/cmake/modules/CheckAtomic.cmake It's possible needing -latomic is more of a compiler issue than specifically being Raspbain/ARM -...

Re-tested with a fresh install / pi, realised the last build I did was on the 32-bit version of Raspbian (backwards compatible with the older pis). On the 64-bit build...

Processor support: Maybe, it is armv7l vs aarch64 but haven't dug into the specifics, think it's also tied into how gcc was built. Detecting it in CMake: Took a little...

Building + linking + basic usage yes Anything that loads shaders - not sure if the vulkan driver is ready yet, but perhaps that's a separate issue. Looks like the...

I think I'm linking glslang yes, but haven't checked that build in a while. The crashes were with the vsgExamples models, which I think are already SPIR-V? Definitely it's a...

Yes, many samples run, basic rendeirng of the teapot, lz.vsgt, etc is fine. The ones that don't hit segfaults in the driver, or other similar failures. Using vsgbuilder as a...

These all seem to function without any unexpected issues: * vsgallocator * vsganaglyphicstereo * vsgarrays * vsgcameras * vsggroups * vsgintersection * vsgmeshshader * Mesh shaders not supported * vsgio...

Latest vsg master as of this morning, vulkan glslang from the system, nothing special there. From the assert and various mesa bug reports I suspect it's something in the driver...

Yep noted that. The slightly newer mesa version I tried previously did change the error messages, so I'm taking that as a positive sign. Haven't booted up the pi yet...