|
Boost : |
Subject: Re: [boost] Back to Boost.SIMD - Some performances ...
From: Michael Fawcett (michael.fawcett_at_[hidden])
Date: 2009-03-26 15:12:58
On Thu, Mar 26, 2009 at 3:08 PM, Joel Falcou <joel.falcou_at_[hidden]> wrote:
> Michael Fawcett a écrit :
>>
>> Joel, how does the extension detection mechanism work? Is there a small
>> runtime penalty for each function as it detects which path would be optimal,
>> or can you define at compile-time what extensions are available (e.g. if you
>> are compiling for a fixed hardware platform, like a console).
>
> I have a #ifdef/#elif structure that detects which extension have been set
> up ont he compiler and I match this with a platform detection to know where
> to jump and how to overload some functions or class definition.
>
> I tried the runtime way and it was fugly slow. So I'm back to a compile-time
> detection as performance was critical.
That's the answer I wanted to hear.
--Michael Fawcett
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk