AVR-Chat

At 03:45 AM 8/01/2009, you wrote:
>Yes.. The world probably will end in 2012, brought about in no small
>part by my conversion to C.
.
>  WINAVR to get going..
.
..add an ICE (50 or mk2) and we better have mass repentance
before it's too late.

Watch out for the "optimizer" (aka code terminator) it will
get you "Time after time" (just to add a musical note).

And if you thought debugging in asm was bad enough..fasten your seat belts!!

Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

Hi John,

> Watch out for the "optimizer" (aka code terminator) it will
> get you "Time after time" (just to add a musical note).

Interesting comment. I almost always compile with -Os and I've not had
any problems at all with the optimizer.

I do embedded linux drivers professionally, and haven't run into any
optimizer issues there either.

Typically, (99.9% of the time) when I hear things like "my code
doesn't work with the optimizer turned on" it's caused by bad code,
not by bad optimizations.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

> ..add an ICE (50 or mk2) and we better have mass repentance
> before it's too late.

I'm running iceless for now, but my experience with atmels ices has
been less than stellar.
(see comments from spring of 08..)

> Watch out for the "optimizer" (aka code terminator) it will
> get you "Time after time" (just to add a musical note).

Yeah, I just saw it do that..

> And if you thought debugging in asm was bad enough..fasten your seat belts!!

while(1)
{
printf("C IS MORE EFFICIENT AND EASIER TO DEBUG AND MAINTAIN.\n");
printf("EVERYONE SAYS SO, SO IT MUST BE TRUE../n");
}

On Wed, Jan 07, 2009 at 04:25:07PM -0500, David VanHorn wrote:
> 
> > And if you thought debugging in asm was bad enough..fasten your seat
> > belts!!
> 
> while(1)
> {
> printf("C IS MORE EFFICIENT AND EASIER TO DEBUG AND MAINTAIN.\n");
> printf("EVERYONE SAYS SO, SO IT MUST BE TRUE../n");
> }

Was "/n" a deliberate goof in the 2nd line?

-- 
David Kelly N4HHE, dkelly@HiWAAY.net
========================================================================
Whom computers would destroy, they must first drive mad.

> Was "/n" a deliberate goof in the 2nd line?

fumblefingers.. :)