[chbot] GCC / Codesourcery #pragma for ARM Cortex M3

[Mark Atherton]

Thanks Richard,

'Attiude' in the context I intended was suggesting a negative 
attitude towards other-peoples-ideas.

What you are proposing is good-solid-engineering !

Anyway, I think my fix is to pull out the very-tight-stuff, drop it 
into a separate module/file and then figure out how to persuade 
Eclipse to treat it differently from the gazillions (2 x 1^g) of 
other files in the system.

Catch up with you Mon, pm.

-Mark

At 11:22 a.m. 16/10/2011, Richard Jones wrote:
>Hi Mark,
>
>I'm going to contradict your without attitude comment from a previous post :-(
>
>I think you have made a good case for test driven development. Write
>automated tests before you write the code and test what you ship. You
>should be able to change optimiser settings at will and see your tests
>still pass. Then you and others are free to re-implement any module at
>will. I like to set the optimiser from day 1. Stepping the code
>through can be an interesting ride with the gcc optimiser on O3.
>
>Its been a good many years since I have detected an optimiser bug,
>although the optimiser does expose bad coding, especially around the
>use of 'volatile'.
>
>Note that tomorrows meeting is in Training Room 2 at 6.30pm as usual.
>
>Richard