Hi,
Maarten Brock schrieb:
> I'm sorry, but I have to contradict this. At one time I
> did have the idea to implement it, but have never made
> it that far. The define _gptrget.c is not
> SDCC_MODEL_MEDIUM but has an extra D
> (DSDCC_MODEL_MEDIUM) (disabled). If I had implemented
> this I cer
On Fri, 02 Jan 2009 14:54:26 +0100
Frieder Ferlemann wrote:
> Hi Mark,
>
> Maarten Brock schrieb:
> > The difference is that medium model puts the variables
> > in pdata and large in xdata. Pdata (max. 256 bytes) is
> > smaller than xdata (max. 64kB) but can be accessed with
> > two pointers
I'm sorry, but I have to contradict this. At one time I
did have the idea to implement it, but have never made
it that far. The define _gptrget.c is not
SDCC_MODEL_MEDIUM but has an extra D
(DSDCC_MODEL_MEDIUM) (disabled). If I had implemented
this I certainly would have put it in the manual.
Hi Mark,
Maarten Brock schrieb:
> The difference is that medium model puts the variables
> in pdata and large in xdata. Pdata (max. 256 bytes) is
> smaller than xdata (max. 64kB) but can be accessed with
> two pointers (r0,r1) what might result in smaller code
> than xdata which only can use d
Happy New Year Mark,
The difference is that medium model puts the variables
in pdata and large in xdata. Pdata (max. 256 bytes) is
smaller than xdata (max. 64kB) but can be accessed with
two pointers (r0,r1) what might result in smaller code
than xdata which only can use dptr.
Maarten
> What
What is the difference between the medium and large memory models for
the mcs51?
The manual text is not clear on the exact differences:
3.17.1.1
...
When the medium or large model is used all variables declared without a
storage class will be allocated into the
external ram, this includes all
