You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So now I reduced my kernel .config that crashes the Go test down to the point where it boots in 1s and doesn't even support PCI. Build the kernel with GCC 6.4.0, Go crashes. 5.4.0, no crash. But I also have *another* full .config that doesn't crash with 6.4.0. The plot thickens.
Now trying to slim down the no-crash .config so I can ultimately diff it and hopefully find the option that makes the difference. And then hope that tells me something useful about the root cause of the crashes.
Ding ding ding it's CONFIG_OPTIMIZE_INLINING, which points back to the compiler. And now I need to figure out which of these function inlining differences is the culprit. https://mrcn.st/p/vxuE2yH4
I think I'm going to wrap gcc with a script that enables/disables that inlining mode depending on a given bit of the hash of the output object file name, then build a kernel for each bit, figure out if it crashes, and narrow down the culprit object file that way.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
