Just a faint idea, but would it be possible to trick the linker into producing the output file (so that we wouldn't have a post-process)? It parses the object files anyway.
Also, I think compiling dsymutil with llvm would give it a slight speed boost (8-10% on our code base in general, hence my guess). Best, Ákos On 9/26/11 6:57 PM, "Greg Clayton" <[email protected]> wrote: >If you are linking a single architecture, unfortunately there isn't much >you can do. Linking DWARF is a serialized process where we take DWARF >from a bunch of .o files and then make a single out file. All DWARF >sections have to be appended to one another and they have >interdependencies, so even though dsymutil does use multi-threading to >parse 8 .o files ahead, it doesn't help in the long run. clang and >llvm-gcc make debug info that is around 4 times bigger that gcc, so this >probably makes things worse for you guys. > >How big is your dSYM file? > >On Sep 26, 2011, at 6:38 AM, Somorjai, Akos wrote: > >> Greg, >> >> Another issue is dsymutil's speed; it takes about 10 minutes to run it >>on >> our main executable, which is more than unbearable. Is their anything we >> can do to reduce that time? >> >> Thanks, >> >> Akos >> > _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
