Re: [Sdcc-user] How to disable pdata?

[Maarten B. <sou...@ds...>]

Scott,

That should do fine. You can also keep an eye on the 
generated .mem file because pdata access does not set 
_XPAGE every time. I usually let make echo it to the 
terminal.

Modifying crtpagesfr.asm may be overkill. The other two 
are required.
OTOH for real paranoia you can use an extra peephole 
file that replaces MOVX @Ri instructions with NOMOVX so 
the assembler will give an error. Or even recompile the 
library with this peephole rule.

No XPAGE equivalent when dual data pointers are 
available is quite common. But it's kind of stupid that 
they made MOVX @Ri totally unusable. If only they had 
fixed pdata to 0x80nn.

HTH,
Maarten

> I'm compiling for a target (Nordic nRF24LU1) which doesn't support
> pdata access -- no equivalent to an XPAGE SFR.  What's the best way to
> disable this feature in SDCC and ensure that my code doesn't
> accidentally get an XPAGE reference?
> 
> Currently my plan is to replace crtpagesfr.asm with an empty
> substitute (so any references to XPAGE cause undefined symbol errors)
> and rewrite crtxclear.asm and crtxinit.asm to not use XPAGE.  (And,
> not use --xstack, of course.)  Is there a better way?
>  --scott
> 
> -- 
>         (http://cscott.net)
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Sdcc-user mailing list
> Sdc...@li...
> https://lists.sourceforge.net/lists/listinfo/sdcc-user
>