optimize function's parameter in c (GCCarm)

Question

i have limited RAM in my microController.(using arm gcc) i should write my code as efficient as possible. consider function blew :

int foo(uint32_t a , float b)
{
    .....
    return 0;
}

so I have two arguments a and b. now if I change the arguments to *a and *b is the function takes less ram than the first function during execution :

int foo(uint32_t *a,float *b)
{
    ....
    return 0;
}

what if the arguments become String or array ( of int, float ....)?? any references would be great. thanks

What does the function do matters, and just by replacing `int` with `int *` you are not going to save memory on stack — Gopi, Feb 04 '15 at 08:42
Here is [a similar question](http://stackoverflow.com/questions/23834823/does-using-global-variables-increase-or-decrease-performance-in-c-code-compiled). It seems a consensus not to use floating point; google/search fixed point. Auselen's answer seems more correct to me; however, VFP arguments might be in different places. Passing argument's in a `struct` pointer **CAN** be more efficient on some ARM CPUs. A pointer is a mini-stack on the ARM as all register address modes are the same. — artless noise, Feb 04 '15 at 18:15
If you want to be space efficient, write a byte code interpreter. Forth is probably a good start. — artless noise, Feb 04 '15 at 18:16
You really need to give a full function for anyone to comment in an definitive way. Making functions `static` and compiling with `-Os` will be helpful. Otherwise, I think you need to give specific code (or a map file) that you need to optimize. — artless noise, Feb 04 '15 at 19:13
this is too vague and even with a little more detail it will still be too generic, you need to just implement your code, build, disassemble, keep track of sizes of things, and then try another approach, see how it compares. float may kill you unless you are using a cortex-m4 then you still have to be a bit careful and more importantly use the right compiler settings otherwise all your effort will be lost in soft float libraries. — old_timer, Feb 05 '15 at 03:31

auselen · Answer 1 · 2015-02-04T10:22:29.890

ARM's Procedure Call Standard defined in Application Binary Interface (ABI) states that the first four word-sized parameters passed to a function will be transferred in registers R0-R3.

Since pointers are also 32-bit in size, there is not that much difference between these two signatures.

int foo(uint32_t a, float b)
int foo(uint32_t *a, float *b)

Both will have a in r0, b in r1 and return value in r0 again.

ARM is a RISC architecture it has many registers and with trivial functions you may even get away from touching any memory at all.

If you are working with micro controllers it is a better idea to check if you should really use floating points. Since they might not be natively supported by the core you are targeting for.

I would check ARM Cortex-A Series Programmer's Guide (most of it applies to micro controllers as well), especially chapters 15 and 17 to learn more about tricks for ARM application development.

user694733 · Accepted Answer · 2016-09-22T11:28:57.560

You can actually waste memory when using pointers. This is for 2 reasons.

1. Register optimization lost

Code which calls foo must take address of the variable to pass as parameter. If passed variable is local, it could be in register but because you take its address it must be placed on stack. In general, using variable in register is faster than using variable in stack.

2. Value of variable unknown after call

When you give address of variable function, compiler no longer knows if variable is modified, and must refresh it if it's read again.

 uint32_t u = 1;
 float f = 2.0f;
 foo(&u, &f); // 1. Address taken, u and f cannot be register variables
 // 2. What is value of u now? It must refreshed from memory before addition happens
 u++;

Bottom line: do not take address of primitive types unless you have to.

Strings and arrays are already passed using address, so there is no other option.

optimize function's parameter in c (GCCarm)

2 Answers2