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. > 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. Maarten ------------------------------------------------------------------------------ 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
