[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-libc-dev] Re: bug #22163 (atomic not working asexpectedinC++)

From: Weddington, Eric
Subject: RE: [avr-libc-dev] Re: bug #22163 (atomic not working asexpectedinC++)
Date: Wed, 9 Jun 2010 13:58:28 -0600


> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Joerg Wunsch
> Sent: Wednesday, June 09, 2010 1:50 PM
> To: address@hidden
> Subject: Re: [avr-libc-dev] Re: bug #22163 (atomic not 
> working asexpectedinC++)
> As Weddington, Eric wrote:
> > As a side note, wouldn't declaring some_temp_variable as volatile
> > solve the issue above?
> I think it does, but it's another pessimization...  It forces the
> function to get a stack frame even if it otherwise doesn't need it,
> and adds memory access cycles.  The optimizer could perfectly keep the
> variable in a register, it's just that the developer intended to move
> the time-critical routine outside the interrupt block.

Ah, I see your point now. Agreed.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]