mirror of
https://github.com/cc65/cc65.git
synced 2024-07-04 13:29:35 +00:00
0ee9b2e446
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.
32 lines
797 B
ArmAsm
32 lines
797 B
ArmAsm
;
|
|
; Ullrich von Bassewitz, 2003-08-12, 2005-04-16
|
|
;
|
|
; Place to store the current working directory.
|
|
;
|
|
; __cwd is initialized by a platform specific function named "initcwd" called
|
|
; by the constructor defined in this module.
|
|
;
|
|
|
|
.export __cwd
|
|
.export __cwd_buf_size
|
|
.constructor cwd_init
|
|
|
|
.import initcwd
|
|
|
|
.include "stdio.inc"
|
|
|
|
__cwd_buf_size = FILENAME_MAX
|
|
|
|
cwd_init := initcwd
|
|
|
|
.segment "INITBSS"
|
|
|
|
__cwd: .res __cwd_buf_size
|
|
|
|
|
|
; NOTE: Some of the code working with directories is not able to handle
|
|
; strings longer than 255 chars, so don't make __cwd larger than 256 without
|
|
; checking the other sources.
|
|
|
|
.assert __cwd_buf_size < 256, error, "__cwd_buf_size must not be > 255"
|