Linked by Thom Holwerda on Wed 27th Apr 2011 21:25 UTC, submitted by foldingstock
BSD and Darwin derivatives This release supports a much larger variety of hardware and multiprocessor systems than previous releases, thanks to updates of ACPI and APIC and ACPI interrupt routing support. Hammer volumes can now deduplicate volumes overnight in a batch process and during live operation. The 'hammer dedup-simulate' command can be used to estimate space savings for existing data. DragonFly now uses gcc 4.4 as the default system compiler, and is the first BSD to take that step. DragonFly now offers significant performance gains over previous releases, especially for machines using AHCI or implementing swapcache(8).
Thread beginning with comment 471483
To view parent comment, click here.
To read all comments associated with this story, please click here.
evilsjg
Member since:
2006-03-29

In the DragonFly camp we are very excited about clang (and pcc), but there is an astounding amount of work to be done without massaging our codebase and toolchain to support the latest compiler-of-the-week. Committing to recent GCC releases yields performance improvements as well as better / more thorough warnings and errors, etc., without committing to the huge amount of work required to switch base system compilers. I am sure the DragonFly project will one day switch to one of Clang or pcc, but probably not until one of those compilers has proven itself as the system compiler of another BSD for a period of time, at which time we will be able to weigh the benefits against the pain of their experience in switching.

Currently, the only MAJOR benefit in switching to one of these alternatives is the license. The DragonFly project is simply taking a bit of a pragmatic approach toward this issue. It is perhaps because DragonFly BSD does not support any commercial derivatives that we have this luxury.

Reply Parent Score: 1

pfgbsd Member since:
2011-03-12


Currently, the only MAJOR benefit in switching to one of these alternatives is the license. The DragonFly project is simply taking a bit of a pragmatic approach toward this issue. It is perhaps because DragonFly BSD does not support any commercial derivatives that we have this luxury.


Well it's not ready for release yet but the performance benefit derived from the new gcc wrt clang is just about 10% (and clang sometimes beats gcc).

The warning and bug detection facilities in clang are way better, but there is another advantage: blocks support. FreeBSD supports GCD out of the box.

That said, I don't complain about Dragonfly adopting gcc4.4 ... I just find it amusing that they take so much pride on it when there's no technical merit just because the other BSDs chose not to do it. As I wrote before, for Debian it was apparantly not a big deal to ship FreeBSD's kernel with a newer gcc.

Reply Parent Score: 1