@@ -16,6+16,8 @@ The [DragonFly snapshots](http://avalon.dragonflybsd.org/snapshots/) are built u

The process of testing [poudriere](https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/index.wiki), a tool for mass-producing binary dports packages, exposed stability issues when repeatedly mounting and unmounting many tmpfs systems on large multicore (48) systems. These issues have been fixed. In addition to stability, several changes were made to improve performance in situations with heavy processor and disk usage.

+Improvements in [poudriere performance, tmpfs performance](http://lists.dragonflybsd.org/pipermail/kernel/2013-April/031224.html), and [CPU usage](http://lists.dragonflybsd.org/pipermail/kernel/2013-April/031227.html) (graphs are linked in those message) were graphed by Francois Tigeot and posted on the kernel@dragonflybsd.org mailing list.

+

### New default compiler

The two base compilers have swapped roles. GCC 4.7, introduced as an alternative compiler with Release 3.2, is now the primary compiler used to build DragonFly. GCC 4.4 remains on the system and still has an important role as the primary DPorts compiler. GCC 4.7 brings [OpenMP](http://http://openmp.org/) (parallel programming) support to DragonFly via libgomp as well as stack smashing protection via libssp, neither of which was supported by GCC 4.4. The newer compiler also offers improved C++ and Objective-C support, and introduces [Link-Time Optimization](http://en.wikipedia.org/wiki/Link-time_optimization) (LTO) support.