Error 71 out of ROM using 16F887

[rovtech]

My main question is why only half of the PIC16F887 is being used?

I am getting an Error71 Out of ROM, A segment or the program is too large MAIN
I was using a PIC16F884 which has 4k of program memory (I assume this is what the compiler is referring to). I switched to a PIC16F887 with 8k of program memory but could only add a few simple statements before the same error returned. The highest address in .lst is 0FE7 which is less than 4k, and nowhere near 8k. (edited; PIC16F874 and PIC 16F877 changed to PIC 16F884 and PIC 16F887).

In this forum I read “Error 71 Out of ROM problem” and “Error 71 ... Out of ROM, A segment or the program is too lar” and have some idea of where the problems are.
Is the code in .lst shown before the statement or after it? I see a lot of code at the start followed by “#include <math.h>"
I’m not shure what constitutes a function. MAIN is a function, does it have to all fit on one page? Much of my program is in a while(1) loop, is this a function to fit on one page?

The exact error is:
Executing: "C:\Program Files (x86)\PICC\Ccsc.exe" +FM "Console PIC_1_v5.1 CMPS11.C" #__DEBUG=1 +ICD +DF +LN +T +A +M +Z +Y=9 +EA #__16F887=TRUE
*** Error 71 "Console PIC_1_v5.1 CMPS11.c" Line 772(4,5): Out of ROM, A segment or the program is too large MAIN
Seg 00004-007FF, 0169 left, need 00761
Seg 00800-00FFF, 0800 left, need 00867
Seg 01000-017FF, 0800 left, need 00867
Seg 01800-01EFF, 0700 left, need 00867
Seg 00000-00003, 0000 left, need 00867 Reserved
Seg 00004-007FF, 0169 left, need 00867

All my functions are very short and simple and are at the end. I sort of understand that 0004 to 07FF needs more ROM but how do I "shorten" blocks of less than 10 statements, often less than 5?
Are segments the same as addresses? Are they in HEX? Why is nothing above 4k used (0FFF, below)?

The .lst file shows:
CCS PCM C Compiler, Version 5.055, xxxxx 26-Jun-17 16:26

Filename: C:\Users\user\Documents\ROV_2 Console\Software Console PIC 1\Console PIC_1_v5.1 CMPS11.lst

ROM used: 3699 words (47%)
Largest free fragment is 2048
RAM used: 93 (26%) at main() level
134 (38%) worst case
Stack used: 2 locations
Stack size: 7

and the addresses are below for continuous blocks with parts of the code and comments shown where they occur. I don't know what the code is after the data.
0004 to 00FD DATA
0228 to 02AA code
035F to 042E code
04B0 to 068A code
#include <math.h>
#fuses INTRC_IO, NOWDT, PUT, NOPROTECT, BROWNOUT, MCLR, NOLVP
#use delay (clock=8000000)
00FE to 0111 code
#use rs232 (baud=9600, parity=N, bits=8, enable = pin_E2, xmit=pin_C6, rcv=pin_C7, ERRORS)
0465 to 047C code
049F to 04A8 code
#use I2C (master, SCL=PIN_C3, SDA=PIN_C4)
0112 to 015B code
0314 to 035E code
#byte porta = getenv("SFR:PORTA") to void main(void)
0800 to 0911 code in various short blocks
while (1)
0912 to 0CD4 code
// Start of data transmission
0CD5 to 0D16 code
// Start of LCD display loop
0D17 to 0FE7 code
// end of while loop
// end of main loop

// functions
047D to 04AF code
0440 to 0454 code
042F to 043F code
0455 to 0464 code
015C to 019A code
01DF to 0227 code
019B to 01DE code
02AB to 0303 code
0304 to 0313 code

[PCM programmer]

[rovtech]

Thanks PCM Programmer.
My mistake. I was using 16F874 a few years ago then switched to 16F884 and of course meant 16F887. I just had 74 in my head. The compiler would not allow such a typo. I corrected the original post with a note.
I understand what you say and saw that in the previous posts I mentioned. I think the problem is in my MAIN function which is easy to make too long. The question is how do I make it shorter? I cannot have more than one MAIN, but I could try to move some statements to separate functions which seems dumb when they would only be called once.
The only floating point is shown below. Does the compiler install the entire math package or just what it needs? This is in MAIN.

[asmboy]

The wise counsel from PCM_P is to
break up your main();
into a number of smaller functions-

just don't get tricky and use the
#inline directive or your work will go for naught.....

[rovtech]

I spoke to a C programmer and he set me straight. I am doing it all wrong and will pass on his words of wisdom for others who might be as confused as I am.
A 'C' program should be a collections of calls to functions that perform certain tasks. Think of it like building a house:

Buy the land.
Dig the basement.
Build the basement.
Install the floor.
Build the walls.
Install the roof.
Wire the house.
Plumb the house, etc.

The above would be your MAIN program and each line would be a function call.
The function "Install the roof" would consist of "draw the trusses, make the trusses, hoist them onto the walls, position them, etc.

So what I need to do is break down my MAIN program into:
Initialize the 3 LCDs.
Read switches and pots
Send commands to arm
Display arm positions, etc

I always thought subroutines (or functions) should only be written for actions that need to be called more than once. I suppose K&R say this but I just flipped thru the first few pages and it is not that clear to me. The only formal training I had was a Fortran course in the '70s but that did not leave me with a lasting impression of putting everything into subroutines. I guess having to declare the variables in each function was not as easy as declaring them all in MAIN. I knew to limit global variables. Fortunately what I have is what I thought was 'structured programming' so big blocks of my program can be easily made into functions. The light just went on!
I need to reduce my 7 pages of MAIN to less than a page.

[rovtech]

My basic problem was that my MAIN function grew too big to fit on a page of the PIC16Fxx and doubling the number of same-size pages did not solve the problem.
My next problem was a lack of understanding pointers. Although I re-read the manual, when I attempted to convert the following code to a function, I hit a brick wall because a function can only return one variable. I needed to return five.