Re: [avr-gcc-list] COMPILER Frame pointer bug!!!

[Dmitry]

Fellows!

The code is Ok, but it seems to me, that I got an interrupt on the SP update.

But anyway I think that lines out __SREG__,__tmp_reg__ and out __SP_L__,r28 
should be swapped.
... also, I think that stack pointer should be latched by hardware during 
read/write operations.

Thanks for all who replied

Dmitry




> At 21:26 17/11/2001 +0300, dimmy wrote:
> >Fellows,
> >
> >I found  strange avr-gcc behaviour.
> >
> >If you declare a function with a variable number of arguments or the 
> >number of arguments is over 18 (actually, total number of bytes, required 
> >for arguments) or you allocate over 18 bytes inside the function, then 
> >avr-gcc disables interrupts on enter to the function and does not enable 
> >them anymore.
> >
> >This is valid only in case, when frame pointer cannot be eliminated or 
> >when no optimization enabled.
> <snip>
> 
> 


*********************************************************************
   ("`-''-/").___..--''"`-._     (\       Dimmy the Wild      UA1ACZ
    `6_ 6  )   `-.  (     ).`-.__.`)      Enterprise Information Sys 
    (_Y_.)'  ._   )  `._ `. ``-..-'       Nevsky prospekt,   20 / 44
  _..`--'_..-_/  /--'_.' ,'               Saint Petersburg,   Russia
 (il),-''  (li),'  ((!.-'                 +7 (812) 314-8860, 5585314
*********************************************************************