On Wed, Mar 17, 2010 at 10:29:37AM +0100, Maarten Brock wrote:
> Peter,
>
> >> Yes, stack-auto puts the sloc's on stack too. And you
> >> cannot move slocs to any other memory, because then SDCC
> >> would need sloc's to access those sloc's.
> >>
> > Does that then imply a severe limit on arguments to functions? Using
> > both --model-large and --stack-auto makes the failing code compile (but
> > as noted not run ...).
>
> With all local variables and function arguments on a (very) limited stack
> there is of course a (severe) limit on their amount.
Ah, the light dawns! I'd been assuming that you had an argument stack
in xdata and I just needed to get the arguments on to it. I'm impressed it
does as well as it does if the entire stack has to fit internal memory!
With this and Mark's suggestions I should be able to get further.
Thanks to you both!
>
> > Well I'm here, should code the compiles and runs with --model-medium
> > also run with only --model-large or are there more flags needed for large
> > model (and also a huge model now I inderstand)?
>
> In general code that compiles in medium model should also compile in
> large. Only pointers that expect to point to a certain memory space could
> cause compile errors.
>
Its more than possible something that I've done thats breaking it, I'll
poke around and see whats different when I get time. Tnanks again.
Peter Van Epp
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
