Hi Ed,
How are you planning on building the LLVM / Clang libraries? Will they be
statically linked to the compiler and the debugger, or do you intend to make
them dynamic too? I found about a small slowdown with a dynamic clang, but the
link times were much lower when building.
Currently, the LLVM build is one of the big serialisation points in our build
system (we build each of the individual libraries entirely independently), so
if you're hacking on the build system it would perhaps be nice to build a
single libLLVM (in /lib/private) that could compile all of the LLVM sources in
parallel and then be used by Clang and LLDB (and any LLVM-based binutils
replacements we start to add). This would likely more than offset the
increased build time for LLDB on any multicore system.
David
On 17 Dec 2013, at 22:15, Ed Maste ema...@freebsd.org wrote:
The in-tree snapshot of LLDB is at a point where it's usable and
suitable for wider testing on amd64, and so I intend to enable it by
default in the near future.
Further information on the FreeBSD port of LLDB is on the wiki, at
https://wiki.freebsd.org/lldb
On my desktop LLDB added about 5 minutes to a buildworld and 80MB to
objdir (over a baseline of about an hour and 1.8GB). If you wish to
avoid building it, you can add 'WITHOUT_LLDB=' to src.conf.
-Ed
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
