for BIT in $(seq 0 31); do make clean && rm -f objs.txt && BIT=$BIT make -j9 && cp arch/x86/boot/bzImage kernel_${BIT}.bzimg && mv objs.txt objs_${BIT}.txt ; donehttps://twitter.com/marcan42/status/928571175210323968 …
Show this thread
-
Among the people who use Go daily it's sort of well known that using cgo can be quirky due to all sorts of vague reasons; one learns to expect to pay a performance penalty at best. That runtime VDSO isn't really cgo and that's ok because it makes sense to optimize its performance
It's not cgo and that's why it crashes: because it makes assumptions about the vDSO that are not guaranteed by the C ABI that it will play nicely with Go's stack layout. You can't have your cake (funny stacks) and eat it too (call C code on them).