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

[Richard Jones]

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

On Sun, Oct 16, 2011 at 11:02 AM, Mark Atherton <markaren1 at xtra.co.nz> wrote:
> Hi Volker,
>
> The overall system is 10k lines, many, many modules !!
>
> Thanks for your other comments...
>
> Regards,
>
> Mark
>
>
>>function (10k lines for a function does sound badly structured though)
>>into a separate module, you can use different switches.
>
>
> _______________________________________________
> Chchrobotics mailing list Chchrobotics at lists.linuxnut.co.nz
> http://lists.ourshack.com/mailman/listinfo/chchrobotics
> Mail Archives: http://lists.ourshack.com/pipermail/chchrobotics/
> Web site: http://kiwibots.org
> Meetings 3rd Monday each month at Tait Radio Communications, 175 Roydvale Ave, 6.30pm
>
> When replying, please edit your Subject line to reflect new content.
>