We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Refer to http://www.keil.com/demo/limits.asp
ARM Evaluation Tools:
Point 4: The debugger supports programs that are 16K Bytes or smaller.
Point 9: The CARM compiler, assembler, and linker are limited to 16K Bytes of object code. Source code may be of any size.
My source file (.c) size is 2KB. After compilation, its object file is of 21KB.
But, I still run the debugger successfully ?
Was there every any actual problem, or was it just a question/observation?
Below is just our thought, maybe wrong, we are not graduated from Computer Science.
We add three more command lines in main program:
i = 1; j = 2; k = i*j;
the code size will have an increment of 20 bytes, after compilation.
We then think code size measurement is in assembly instruction, not in C command.
There is no direct correlation between number of C source lines or number of C statements, and number of assembler instructions generated.
There is no direct correlation between number of assembler instructions and number of code bytes - different assembler instructions has different size.
Code size is number of bytes of processor instructions (machine code).
The processor does not care about if you have written the program using assembler instructions or if you have used a high-level language. All it cares about is the contents of the individual code bytes. The limits for the evaluation version of the Keil tools don't care about number of lines of assembler or number of lines of C. They care about number of bytes of produced machine code for the processor to run.
Thanks much, it is clear.