We haven't looked at libdispatch specifically; would welcome your feedback on how we compare.

We hope we do well here; we've had some nice results: https://github.com/facebook/libphenom/commit/c2753c2154a0cff...

That looks nice.

I used libdispatch to prototype a server and would be great to compare with other libraries before starting the project.

libPhenom seems to have much more features, maybe even more than I need, but the documentation seems good. I will try to make another prototype with your lib.

Thanks.

This is the test code referenced by that commit: https://github.com/facebook/libphenom/blob/master/tests/tpoo...

Why do you do -fno-omit-frame-pointer on x86_64 the ABI requires dwarf or is there something I'm missing?

Frame pointers make things easier for tools to get backtraces without requiring complex dwarf unwinders. The observability is something I value more than not being able to use that register for other things.

Functionality: Well, libdispatch doesn't really work outside of OS X, and this is primarily targeted at Linux server apps.

I can't comment on performance.

Also, it doesn't look very active: https://libdispatch.macosforge.org/trac/log/

libdispatch works on FreeBSD (https://wiki.freebsd.org/GCD) and on Linux (http://packages.debian.org/wheezy/libdispatch-dev), but I don't know if blocks works on Linux.

If you use clang you get blocks:

http://stackoverflow.com/questions/5907071/clang-block-in-li...

The library may work, but Grand Central Dispatch, which is the whole point, is really an OS X thing. BSD may have adopted it, not sure. I'm pretty that confident Linux has not.

Grand Central Dispatch is just the marketing name for libdispatch. The do use pthread work queues if available, which they are on OSX & BSD. On linux a thread pool is used

Yes, so there's absolutely no reason to use it if you're primarily targeting Linux.