Re: [boost] [context/coroutine] split into two libs in trunk?!

Am 14.04.2012 00:37, schrieb Giovanni Piero Deretta:

Having said that, I doubt that on a modern CPU this extra state save/change would hardly cost more than an extra 50% on a context call (which in the grand order of things isn't really that much). Any claimed scalability differences between boost.context and the my old library must come from somewhere else and not from the low lever context switching routines.

boost.context uses a lot of BOOST_ASSERT-statements for testing pre- and postconditions taking care about the internal state of the context. of course without defining BOOST_DISABLE_ASSERTS you measure the extra cycles of the pre-and postconditions tests too.