Hallo Kiste,
On 12/27/11 10:00 am, Oliver Seitz wrote:
Yes, there have been discussions about this already. I think it is a
pity to waste RAM that could easily be made accessible.
That's the idea!
Memory allocation is a confusing subject anyway, especially when
large structures are used.
Thanks for the examples! I have never digged so deep in the issue!
Memory allocation is primarily the concern of the compiler.
My concern is to specify the available RAM and declaration of
compiler-required variables in such a way that the compiler can make
optimal use of all available RAM, taking into account the limitations of
the compiler and the PIC architecture.
I would appreciate the usage of as much RAM as possible. Even better
than declaring a new chunk of RAM for the shared bytes would be to add
the shared bytes to the largest unshared data block. This way not only
the overall number of bytes, but also the maximum structure size would
be increased.
As far as I know (I've discussed this with Kyle a long time ago) it
doesn't make a difference for the compiler how RAM is specified with
pragma data. The compiler combines adjacent chucks to contiguous blocks.
Therefore it is important that the compiler required variables
(_pic_accum and _pic_isr_w, which must be in shared memory) are located
such that memory fragmentation is avoided when possible.
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
