On 10. 01. 2013 18:09, Raphael Neider wrote: ... > So code generation is ready (and a lot of things actually just fall > into place -- its magic :-D). > Did you also already use overlapping SFR definitions (TMR1 and TMR1L above)? ...
As /sdcc/device/non-free/lib/pic14/libdev/* is created in sdcc build stage, and source files didn't contain sfr16 keyword, this work as without patch. Next in install stage we can change extern declaration __sfr TMR1 to __sfr16 TMR1 without touching TMR1L and TMR1H in device include files. Effects you see in example from previous post. And yes, user can use TMR1, TMR1L and TMR1H together. If we want exclude libdev and define SFR in user programs (want we?) TMR1 conflicts with TMR1H ( if use __sfr16 for TMR1) To avoid this we can patch file sdcc/src/pic14/glue.c (comment out instruction for size increment, line 210). But i'm not sure for all side effects now. And this is not necessary in my opinion. Albert ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
