Re: [Sdcc-user] PIC forcing variables to be on the same bank

2014-06-23 Thread Gál Zsolt
Hello Raphael, This was new for me also. It would worth to write about it in the sdcc manual. Regards, Zsolt -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big

Re: [Sdcc-user] PIC forcing variables to be on the same bank

2014-06-22 Thread Kustaa Nyholm
urceforge.net>> Date: Mon, 23 Jun 2014 07:14:09 +0300 To: "sdcc-user@lists.sourceforge.net<mailto:sdcc-user@lists.sourceforge.net>" mailto:sdcc-user@lists.sourceforge.net>> Subject: Re: [Sdcc-user] PIC forcing variables to be on the same bank struct

Re: [Sdcc-user] PIC forcing variables to be on the same bank

2014-06-22 Thread Raphael Neider
Hi, I would have to look at the compiler's source code for details. What should work is to group the variables into a structure like struct { char counter; short NCO; short SPEED; short OLDV; /*... */ } grp; and to access them via grp .NCO += grp.SPEED; You could of course introduce macros to

[Sdcc-user] PIC forcing variables to be on the same bank

2014-06-22 Thread Kustaa Nyholm
Hi I'm trying to optimise a critical section of my code and to get rid of the BANKSEL instructions I would like to place variables on the same bank. I tried: #pragma udata bank2 COUNTER NCO SPEED OLDV char COUNTER; short NCO; short SPEED; short OLDV; ... NCO += SPEED; ... But this compile