4 ms·
One fun bug / issue I’ve been working on recently is that clang / llvm-mc (the llvm assembler) don’t handle dwarf data the same way as gcc. This can creat some
by carterschonwald 8y ago
One fun bug / issue I’ve been working on recently is that clang / llvm-mc (the llvm assembler) don’t handle dwarf data the same way as gcc. This can creat some issues if you’re using gcc on OS X, where the system assembler IS the llvm assembler. Even after this, there’s other misadventures with having dwarf data pass validation with the Apple/llvm linker.
My context is making sure that the main Haskell compiler, ghc, has an approximately 15 percent faster runtime system on OSX with c code built with GCC than with Clang. So I’ve been tracking down how to how to continue supporting that build combo while making sure dwarf / gdb suport in Haskell still works.
https://ghc.haskell.org/trac/ghc/ticket/15207 https://ghc.haskell.org/trac/ghc/ticket/15207