code size VS speed optimization setting?

[Kamikaze47]

yeah ive written a program nearly 3000 lines long, and ive hit the end of the 32k of code space my PIC has. I pulled all the strings out into EEPROM and that saved some space, but im likely to run out again soon. I've done the most obvious things to save space.

*edit* i guess the only thing left to do is go thru all 3000 lines looking for where i can make it more efficient... *sigh* that will be a chore

[mackrackit]

Just a thought...
Move some of the routines over to another PIC, Maybe something that has some heavy calculations. PIC#1 sends data to PIC#2 for calcs, when finished PIC#2 sends data back to PIC#1. Sort of like an interrupt.

[skimask]

yeah ive written a program nearly 3000 lines long, and ive hit the end of the 32k of code space my PIC has. I pulled all the strings out into EEPROM and that saved some space, but im likely to run out again soon. I've done the most obvious things to save space.
*edit* i guess the only thing left to do is go thru all 3000 lines looking for where i can make it more efficient... *sigh* that will be a chore

Have you tried moving the most commonly used variables to BANK 0? (only applies if you're using a 16Fxxx series PIC, doesn't do anything on an 18Fxxx series)

[Kamikaze47]

using an 18F4550

I would just get a pic with more code space. but i need the USB functionality of the 4550.

[skimask]

using an 18F4550
I would just get a pic with more code space. but i need the USB functionality of the 4550.

Repeat...Until uses less space than a For...Next, about 3 bytes for each one...

Multiplies and Divides by power's of 2 can be replaced by shifts << and >> ...

For...Next loop that are (for instance) "0 to 7" take up less space than "1 to 8", again, only a few worth...

[Kamikaze47]

thanks for the tips

i'll go thru my code

*cringe*