From: Shawn Jefferson (sjefferson_at_sd62.bc.ca)
Date: 2003-04-24 17:48:06
While we are on that subject, how about taking the EXEHDR definition for the Atari target and putting that in a separate file as well? For that matter, probably AUTOSTRT too.
Now that I've looked at this again, I realize what my issue was. I had a program that had to load itself into two separate memory areas ($2000-3FFF and $8000-BC1F) leaving the $4000-7FFF area alone. On the Atari you can have multiple segments in your exe file. The problem I ran into is that the EXEHDR in crt0.s is hardcoded like so:
; EXE header
.segment "EXEHDR"
.word $FFFF
.word __CODE_LOAD__
.word __BSS_LOAD__ - 1
So, in my first segment I *have* to have my code segment first and my bss segment last, unless I want to have my own crt0.s file, which I don't since then I have to keep updating my code with library changes (I think there were two major upgrades to the atari library during the writing of my application.) Thus my heap area is stuck in this small memory area (2000-3FFF) as well (?)
I thought if you could make this more easily configurable it would be nice (in a separate thread you said that wasn't possible though.)
¯
Shawn
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2003-04-24 17:52:50 CEST