[Ardour-Dev] weird asm error on core2 in FPU_OPTIMIZATION code (2.0-ongoing)

Jörn Nettingsmeier nettings at stackingdwarves.net
Sun Jun 21 14:59:13 PDT 2009

Paul Davis wrote:
> 2009/6/21 Jörn Nettingsmeier <nettings at stackingdwarves.net>:
>> i see. thanks for the clarification. i'll file a heads-up bug in mantis
>> with this explanation in it, so that people who run into this issue have
>> a chance to find it. maybe in the future a more robust way to determine
>> bit width can be found - or maybe 32/64 bit systems will just die out...
> the problem is that there is no "right" or "more robust" way to do
> this - its really a choice. 

sure. the problem is that compilation will fail if people run a 32bit OS
on a 64bit capable CPU, that's how i got the error. (i think.)

maybe the most "robust" way is to ask the assembler what it thinks is
best (because it's the assembler that causes the error...)

> you can (a) optimize the app for the CPU
> that you appear to have or (b) don't try to be clever about that, and
> leave gcc to do it "well enough" or (c) provide your own flags. by
> default, ardour's build system picks (a). FPU_OPTIMIZATION is
> equivalent to (b) and ARCH is equivalent to (c).

i see. maybe a note in the README would be enough. am i guessing
correctly that ARCH is something like CFLAGS in the autotools world? so
anything that cpp takes as -march or -mcpu would be ok?

Jörn Nettingsmeier

Verantwortlicher für Veranstaltungstechnik

Audio and event engineer
Ambisonic surround recordings

+49 177 7937487

More information about the Ardour-Dev mailing list