Re: [sdcc-devel] Why are auto variables not allocated on the stack for the hc08 port?

[Frieder F. <fri...@we...>]

Hi,

Am 08.01.2012 18:24, schrieb Patryk:

> ----- Original Message -----
> From: "Erik Petrich"<epe...@iv...>
> To:<sou...@ds...>; "Development chatter about sdcc"
> <sdc...@li...>
> Sent: Thursday, January 05, 2012 10:03 AM
> Subject: Re: [sdcc-devel] Why are auto variables not allocated on the stack
> for the hc08 port?
>
>
>>
>> On Thu, 5 Jan 2012, Maarten Brock wrote:
>>
>>>> Looking back, I am ambivalent; some days I regret this decision and
>>>> others
>>>> not. At this point I mainly would worry about backwards compatibility if
>>>> --stack-auto were no longer the default. If we change the default,
>>>> perhaps
>>>> we could also add a new option --data-auto to force the older behavior.
>>>
>>> I would prefer to use --fix-auto or --fixed-auto as I
>>> think it is about putting auto variables on stack or at
>>> a fixed adress.
>>
>> I'd like to have a non-stack option for the auto variables, but I'm not at
>> all committed to a particular name for the option. Your suggestions sound
>> better to me than the one I proposed.

For the mcs51 port with large memory model a mixture of both might be beneficial.

If overlayable functions with auto variables could use data memory (out
of a pool with user specifyable size) instead of having to use xdata only
this would result in much quicker and shorter accesses to these variables.

Greetings,
Frieder