Well, I made the changes, had to hack something up as google turned that
as the only solution so far, though aparently future or maybe latest
cutting edge versions of automake will support per-file
cflags.
Can you check and tell me about your results?
Cheers!
>>>>> Now that's a tricky choice ;-).
>>>> Because of the code generation bug, OPCODE *must* be compiled with
>> -O1. So if you're going to use the same compilation flags for ODE and
>> OPCODE, you're probably better of with -O1 (although it may
>> significantly slow down ODE :-( ). Otherwise OPCODE will be broken.
>>>> Now if you can specify compilation flag separately for OPCODE and
>> ODE, it may be a nice idea to specify -O1 for OPCODE and -O2 for ODE.
>>>> I'm not sure how big is the performance difference with -O1 vs -O2
>> for ODE. I don't know ODE enough to know whether the auto-tuned *.c
>> files are going to make ODE slower with -O2 instead of -O1 (used for
>> ODE as a whole).
>>>> As a side note, I think it would be interesting to see how GCC 4.0
>> performs with -O1/O2 on those autotuned *.c files.
>>>> Cheers,
>>>> Tanguy
>> _______________________________________________
>> ODE mailing list
>>ODE at q12.org>>http://q12.org/mailman/listinfo/ode>>>>>> _______________________________________________
> ODE mailing list
>ODE at q12.org>http://q12.org/mailman/listinfo/ode>>