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
-
.. or vdso failing by making assumptions about rest of userland that're not guaranteed.. :) always_inline + some commentary about expected stack sounds the right thing for these two vdso calls, they're so simple; a go patch to help it work with unusual krnls and gcc is needed too
The spec doesn't guarantee stack usage, so Go is wrong here :-). Of course, that would be a worthwhile addition to the spec. But given the current documentation, this is squarely a Go bug (the source even acknowledges it currently makes an assumption).
-
-
I wasn't saying it's not a go bug, but onus here is on the kernel, as the API provider, to precisely specify behavior, whatever it may be, independently of a particular compiler or flag.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.