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 471338
To view parent comment, click here.
To read all comments associated with this story, please click here.
laffer1
Member since:
2007-11-09

I think we'll see FreeBSD and NetBSD default to llvm, OpenBSD and MirBSD use pcc. DragonFly might win some benchmarks for a while because of this choice.

I haven't decided with MidnightBSD yet, but I'm leaning toward migrating to llvm. The GPLv3 has a few provisions that make me nervous.

Reply Parent Score: 1

reez Member since:
2006-06-28

I think we'll see FreeBSD and NetBSD default to llvm, OpenBSD and MirBSD use pcc. DragonFly might win some benchmarks for a while because of this choice.

Side note: DragonFly BSD was the first BSD booting with an llvm/clang compiled Kernel and Userland or at least one of these two things ;)

Edited 2011-04-30 00:06 UTC

Reply Parent Score: 2

pfgbsd Member since:
2011-03-12

Side note: DragonFly BSD was the first BSD booting with an llvm/clang compiled Kernel and Userland or at least one of these two things ;)


Uhm... I am not sure of that, but I would think Apple Darwin has beat all the other BSD variants there ;) .

Reply Parent Score: 1

evilsjg Member since:
2006-03-29

FreeBSD ( http://lists.freebsd.org/pipermail/freebsd-current/2009-February/00... ) beat DragonFlyBSD ( http://leaf.dragonflybsd.org/mailarchive/kernel/2009-03/msg00067.ht... ) to a self-hosting clang-built kernel by about 3 weeks. Both of which were well ahead of Linux ( http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-October/011711.html ). Apple made the transition to Clang with the Snow Leopard release in June of 2009. While it may seem reasonable to assume that Apple had internal builds going well before 4-5 months in advance, the blockers that were fixed in Clang and allowed these BSD derived kernels to build and boot were fixed in early 2009 -- OSX was probably building and booting in the same timeframe as FreeBSD and DragonFly.

Reply Parent Score: 1