The compiler output tells me that my application uses 472 bytes of RAM, but the listing file reports an extra 3112 bytes, for a total of 3584 bytes. I'm assuming that the discrepancy is due to system calls and other internal workings of the virtual machine.
I'm curious though, if the compiler output could reflect this true number, i.e. give me a breakdown of the actual RAM usage rather than just the amount used by the variables in my application.
-Don
RAM Usage Reporting
I get this type of output:
Did you misread the listing file? Perhaps you can post an example (sans code) so we can see what you mean.
Code: Select all
Code: 35 bytes, RAM: 1 byte, Persistent memory: 0 bytes
Target Device: ZX24a, Minimum VM version: v1.1.2
RAM size: 3584, heap size: 256
Mike Perks
Re: RAM Usage Reporting
Are you perhaps referring to the last line of the .lst file that looks something like this:Don_Kirby wrote:The compiler output tells me that my application uses 472 bytes of RAM, but the listing file reports an extra 3112 bytes, for a total of 3584 bytes.
Code: Select all
RAM size: 3584, heap size: 256
You'll find more information on RAM use in the .map file. For each task, it gives an estimate of the stack space needed. For each routine, it itemized the local variables (that contribute to stack use).Don_Kirby wrote:[Can the compiler] give me a breakdown of the actual RAM usage rather than just the amount used by the variables in my application.
- Don Kinzer
Re: RAM Usage Reporting
That makes much more sense.dkinzer wrote: That is indicating the amount of User RAM that is available, not how much is being used.
-Don