basically no. I thought to do this check, but somehow forgot it.
however, on a function entry you can check r1 value and compare it with 
__bss_end.

~d

On Tuesday 15 April 2003 14:40, Malan Joubert wrote:
> Seems like a more difficult problem than I thought! Would a simulator be
> able pick this kind of error up?
>
> Quoting Dmitry <di...@mail.ru>:
> > precisely, Steve.
> > stack overflow is a very annoyng thing.
> > However there one can see, if something really stupid has been done.
> >
> > Actually, 3-current gives some info on max stack usage within a file...
> > this does not take into account nested calls.
> >
> > ~d
> >
> > On Monday 14 April 2003 19:19, Steve Underwood wrote:
> > > Not really, Dmitry. That gives you no clue as to whether there is
> > > sufficient RAM for the stack.
> > >
> > > Static worst case stack analysers used to be a part of many embedded
> > > system compilers in the 80s. Now, they seem to have gone. There were a
> > > *very* valuable tool.
> > >
> > > Regards,
> > > Steve
> > >
> > > Dmitry wrote:
> > > >hi Malan,
> > > >linker will bark with a message like:
> > > > msp430-ld: address 0x5026 of a.out section .bss is not within region
> >
> > data
> >
> > > >Also, you can check a memory utilization with
> > > >msp430-size.
> > > >
> > > >~d
> > > >
> > > >On Monday 14 April 2003 17:32, malan wrote:
> > > >>Hi
> > > >>I'm new to msp-gcc (I used IAR until now). The free compiler
> >
> > looksreally
> >
> > > >>cool. I just have one question... What happens when I have more
> >
> > variables
> >
> > > >>than the MSP's RAM can hold. E.g. an array: float someArray[100000]?
> >
> > Will
> >
> > > >>the compiler tell me that I'm being stupid or must I check through my
> > > >> whole program and make sure I'll never exceed this limit? I know
> > > >> this
> >
> > is
> >
> > > >> a stupid question but I really don't know!
> > > >>
> > > >>Thanx,
> > > >>Malan Joubert
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Mspgcc-users mailing list
> > > Mspgcc-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> >
> > --
> > /********************************************************************
> >      ("`-''-/").___..--''"`-._     (\   Dimmy the Wild      UA1ACZ
> >       `6_ 6  )   `-.  (     ).`-.__.`)  Enterprise Information Sys
> >       (_Y_.)'  ._   )  `._ `. ``-..-'   Nevsky prospekt,   20 / 44
> >     _..`--'_..-_/  /--'_.' ,'           Saint Petersburg,   Russia
> >    (il),-''  (li),'  ((!.-'             +7 (812)  3468202, 5585314
> >  ********************************************************************/
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Mspgcc-users mailing list
> > Mspgcc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
> -------------------------------------------------
> Pietas Mail
>
> Server configured by
> DataCore
> Malan Joubert
> 05/2002
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users

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


Reply via email to