From: Patrick E. <pa...@pa...> - 2001-08-16 10:31:59
|
On Thursday 16 August 2001 00:36, you wrote: > Oops. I thought I did the cvs add for that file a long time ago, > but I didn't. It's there now. Good stuff, I got it now. > > Are static local variables also included in the fixed global > > memory? > > I think so, although I'm not sure if they are in there yet. Is > that the way it is normally done? Well, they must maintain their state throughout the execution of the program. That means they must have their own storage location. All of the non-automatic storage locations, including globals and statics, must be initialized to zero. > > In 6.1.3 are the MATHx variables the size of the largest basic > > type (ie. not arrays/structures)? > > Yes. I'm not sure if this is implimented yet, but the idea was > that the compiler would check for the largest used type, and create > the MATHx registers this size. Right now it may just be #define'd > somewhere. > > > Are function return addresses really placed on the stack? What > > about function return values? > > I think the current code uses the hardware stack (for the PIC > instruction set). With the AVRs, it looks like a real stack (no > hardware limits) will be possible. I would like this to be > configurable, but it isn't yet. I think right now function return > values are always in MATHB. MATHB is kind of the central point for > all memory movement. > > I'll be looking at gra1.y and gra_util.c next, since that is > where the work to be done is. Do you know what needs done yet? It would be cool if you could think of a few coding tasks to let me familiarize myself more with your code. Do you want to integrate what you said to me in your last e-mail into the doc, or should I do that? I think perhaps it would be a good idea to watch for interesting information in our e-mails and add that to the docs as necsessary. Have a nice day! :) Patrick Earl - pa...@pa... |