| ??? 11/21/06 08:57 Read: times |
#128340 - this is still my fixation to asm.... Responding to: ???'s previous message |
Jez Smith said:
I assume from the use of the word heap that you want to use malloc and have got dynamic data sizes going on, in which case erm.....dunno you could dynamicaly calculate the memory after malloc has messed around with it which should be fun. Certainly; however, I didn't want to have so much of that fun at this stage... I am still fixed somehow to asm where I would define all my variables using DS or so, then the last such defined variable would in fact point to the rest of available XRAM so I could use of it as much as possible for datalogging or similar. Jez Smith said:
If youve got fixed data structures in XRAM then you just look at the map file to see where they live in XRAM. This is of course the easy, obvious and completely bad way... Why should I look at the map file, can't the compiler do the dirty job for me? :-) I assumed the same as Russ: Russ Cooper said: Of course, SDCC being open source, there certainly is a way how to do it - patch the linker - I just thought there might be some "standard" (read: cheaper :-) ) way how to do it...
There may also be a way to get the linker to define a symbol having the value you want. For now, I simply placed a pointer somewhere above the already allocated memory hoping that the reserve I left there will suffice forever; and made a mental mark to check periodically (which I know for sure I will forget and I will have a lots of fun with conflicts arising from this - thanks heavens this is only a hobby stuff...) Jan Waclawek |
