Subject: Re: [boost] How to structurate libraries ?
From: Joel Falcou (joel.falcou_at_[hidden])
Date: 2009-01-15 12:37:46
Phil Endecott a écrit :
> Very interesting. If you need a motivating problem, have a look at
> the DCT code in libjpeg.
Well ^^ why not :)
> I thought about trying to improve this using gcc's SIMD extensions
> (which I guess you'll use as the back-end of your code on that
> platform, right?) but quickly decided it was too complicated.
SSE2 intrinsics on Intel platform and Altivec intrinsics on PPC
platform. Still have to see how to handle Visual Studio which can't
handle typed vector types properly :/
> (As to the "how to structure libraries?" question, I would prefer to
> make each independent unit a separate library in its own right, even
> if they are small. Bundling things up into collection-libraries will
> tend to hide the contents; see for example today's example of the
> binary constants feature, hidden inside Boost.Utility, and apparently
> undiscovered. I suggest that this SIMD code should be its own
> library, Boost.SIMD.)
Was thinking about this too. But SIMD has a lot of dependencies on other
small library (mainly my Memory one). What would happen if SIMD is
accepted and not memory ?
-- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk