Oliver Schmidt 0ee9b2e446 Changed run location of INIT segment. ... So far the INIT segment was run from the later heap+stack. Now the INIT segment is run from the later BSS. The background is that so far the INIT segment was pretty small (from $80 to $180 bytes). But upcoming changes will increase the INIT segment in certain scenarios up to ~ $1000 bytes. So programs with very limited heap+stack might just not been able to move the INIT segment to its run location. But moving the INIT segment to the later BSS allows it to occupy the later BSS+heap+stack. In order to allow that the constructors are _NOT_ allowed anymore to access the BSS. Rather they must use the DATA segment or the new INITBSS segment. The latter isn't cleared at any point so the constructors may use it to expose values to the main program. However they must make sure to always write the values as they are not pre-initialized.		2015-10-14 22:52:09 +02:00
..
emd
ser
_scrsize.s
banking.s
break.s
cgetc.s
clrscr.s
color.s
cputc.s
crt0.s
crtc.s
devnum.s
extzp.inc
extzp.s
get_tv.s
irq.s
kbhit.s
kclose.s
kernal.s
kiobase.s
kopen.s
krdtim.s
kreadst.s
kscnkey.s
kscreen.s
ksetnam.s
ksettim.s
kudtim.s
libref.s
mainargs.s	Changed run location of INIT segment.	2015-10-14 22:52:09 +02:00
peeksys.s
pokesys.s
randomize.s
revers.s
systime.s
sysuname.s