how are you coping with all the warnings it spews out?
-
-
-
There aren't that many any more. I've taken to sending patches for obvious stuff. https://lkml.org/lkml/2017/11/22/576 …
- End of conversation
New conversation -
-
-
What's the upside of running clang built kernels? (In general, not just on phones)
-
I'm most interested seeing Clang's CFI https://clang.llvm.org/docs/ControlFlowIntegrity.html … and SafeStack https://clang.llvm.org/docs/SafeStack.html … implementations working on the kernel. A lot of academic compiler instrumentation tends to happen with LLVM too, so being able to experiment with those on the kernel is exciting.
-
GCC also don't have MSan and there's a KMSan implementation via Clang for finding uninitialized memory usage bugs: https://github.com/google/kmsan .
-
Clang also provides a robust implementation of UBSan and friends without the pervasive false negatives and false positives from GCC. Android already uses Clang for userspace and third party apps and they're using the integer sanitizer in trapping mode for production.
-
Simply not needing to deal with a secondary toolchain is a big improvement. Android's Clang/LLVM toolchain is 5.x (2017) while the GCC toolchain is still 4.9 (2014) since their migration plan from it has been moving to Clang for a long time rather than ever upgrading it again.
End of conversation
New conversation -
-
-
that is the better option, relying on mobile phones instead of "neutralize leadership"
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.