From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2003-04-23 23:56:59
On Wed, Apr 23, 2003 at 10:31:06PM +0200, Groepaz wrote:
> On Wednesday 23 April 2003 00:24, Shawn Jefferson wrote:
> > I would like to see configurable heap and stack placement too... I think
> > the heap is now defined by the BSS area isn't it, and is hardcoded
> > somewhere in the library?
>
> yes, in crt0.s and _heap.s to be exact :)
I've used the traditional approach for the memory layout, that is, CODE, DATA
BSS and STACK in this order. While this works for architectures with one big
chunk of memory, it gets somewhat difficult, when there are several blocks of
memory, either because this is the actual memory layout of the machine, or
because the existing memory is divided for some reason.
I've already found this to be a problem with Groepaz NES code. Unfortunately,
I don't have an idea for a solution that is 1. easy to handle and 2. easy to
implement. Allowing to define stack and heap in the linker config would work,
but this would need a complete expression evaluation for the linker, so it is
not exactly what I would call "easy to implement". As it looks now, you will
have to live with the existing linker and code, provided that no one has a
better suggestion.
Regards
Uz
--
Ullrich von Bassewitz uz_at_musoftware.de
----------------------------------------------------------------------
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 00:00:39 CEST