I don't know if this will help or not, but I also had a problem with
Large Memory Model and sloc (and parameters) being placed in internal memory.
My problem was solved by using "#pragma NOOVERLAY" which still leaves the sloc/parameters in internal memory, but doesn't overlay them...
----- Original Message -----
From: Michal Strelec <strelec@...>
To: mail list SDCC <sdcc-user@...>
Sent: Tue, 30 May 2000 13:27:03 +0100 (GMT+01:00)
Subject: [sdcc-user] Suggestions for little \sloc\ problem fix
> I was trying to solve problems porting my big project to sdcc and
> stillwas foundig bugs. The biggest problem is with sloc temporary
> variables. I was trying to do tricks (with help from sundeep) like using
> reentrant keyword, using external stack. But Nothings help because of
> stack overflows and other problems.
> Now I wonderr why sloc variables are not in xdata memory I look at source
> files and I won't be (maybe) too dificult to use movx insteed mov.
> Next suggestion is two shere sloc variables between function (but this
> function can't be called each from another). This could help save man
> many internal memory.
> something like --sloc-share func1,func2,func3...
> Please write me back if you think it is worth to do it.
> Sdcc-user mailing list
Get latest updates about Open Source Projects, Conferences and News.