I'm squeezing a large C++ app onto PalmOS 3.5,
testing on POSE set up to emulate a Vx with 8192k
memory.

The CW link map reports:

Data section below A5:  19280 bytes
Data section above A5:   1154 bytes

This appears to be too much.  While I'm able to work
around this problems at the moment, I will soon need
better control over that critical resource.

What I'd like to know is:

1) Can I exercise any control over the size
of the Data section?

2) Can I move any of the things being dumped into
that section to a code segment?

Here are some lines from my map file, together
with my guesses at what they are and how
helpful moving them would be.  I'd appreciate
any help with identifying them and getting
them out of my Data section.

Initialized near data

Data:    -24      24 bytes  "@JumpTable"
Segment jump table.  Even if they can
bo moved, it wouldn't help much.

Data:  -5094      15 bytes  "@506"
No clue.  There are a lot of them, though,
so moving them would be helpful.

Data:  -5117       1 bytes  "@stringBase0"
A literal string.  Surely, these can go to a
code segment?  I don't have many, so
moving them wouldn't be any great boon.

Data:  -5776     376 bytes  "__vt__AClass"
A C++ virtual function table.  They are big, and
there are a bunch of them.  Moving these
would be great.

Uninitialized near data

Data: -17768      12 bytes  "@3183"
No clue.  Lots of them, all 12 bytes.
Moving would be very helpful.

Data: -17769       1 bytes "__init__StaticData"
Static data member.  Moving them would help
a little.

Initialized far data

Data:    210     944 bytes  "__segtable__"
The segment table. Only one of these, and
it's not big enough to bother with.

Data:     40      28 bytes  "@exceptioninfo@"
something to do with exceptions (must be
coming from the library, 'cause I turned
exceptions off).  Only a handful of them,
don't matter.

--
mailto:[EMAIL PROTECTED]
http://www.hgardner.com



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to