3

I searched in web where will be the C macros stored in memory and how does it consumes more memory compared to functions? Could not get any satisfying answer .Can anyone please let me know the asnwer exactly ?

is there any way to find out the memory consumed by a macro in c?

And one more question comes up in my mind is , Suppose i decalre a macro #define START 10. and i have variable int i = 0, which i would be replacing with macro like this i = START. Now int i =0 has already allocated memory in stack and if i place START in place of 0 , it would be a just a reaplacement in the memory previously allocated. So pls tell me how will it consume more memory in this context. I am not sure what i am thinking is correct , if i am wrong , pls correct me .

Previous question asked on this site does not answer to these contexts..

Thanks

pranathi
  • 383
  • 4
  • 6
  • 16
  • Hello haccks, Previous questions is not giving answers to the question i have asked here Thanks – pranathi Jun 16 '14 at 14:19
  • Actually I didn't wanted to close it. I just flaged it for dupe (very close) and it get closed. Reopend now. – haccks Jun 16 '14 at 14:39

4 Answers4

4

Macros are a preprocessor construct. All macros are replaced by their definitions before the compiler even sees the code.

This means that if you use a lot of macros with large replacements, they will generate a lot code. Function calls don't work that way, since they call a single function that only has the code once.

There is no standard way of figuring out how much code is due to macros, no.

unwind
  • 391,730
  • 64
  • 469
  • 606
3

Macros are not stored in memory anywhere in the final program but instead the code for the macro is repeated whenever it occurs. As far as the actual compiler is concerned they don't even exist, they've been replaced by the preprocessor before they get that far.

The reason that this usually takes up more memory is that it gets repeated every time the macro is used. There's no general way to determine how much memory they will take up but, honestly, memory considerations are really not the reason the reason to prefer functions to macros.

If you having a burning need to find out the amount of memory consumed you could approximate it by looking at the disassembly of a place where you use the macro and multiplying the number of times that the macro appears in the source code by the number of lines of disassembly produced. However, there's no guarantee that different uses of the macro or the same use under different circumstances will produce identical code so this can only ever be a crude measure.

Jack Aidley
  • 19,439
  • 7
  • 43
  • 70
1

The values of C macros aren't stored in memory during program execution. Their values are instead copied over to wherever they're used during compilation.

PandaConda
  • 3,396
  • 2
  • 20
  • 22
0

"The reason that this usually takes up more memory is that it gets repeated every time the macro is used."

With a modern compiler depending on the compile settings (FAST CODE/SMALL CODE) it may spot commonly used code and optimize it into a function (SMALL), or it may inline the code for speed (FAST).

It isn't always the case that the code will always be bigger depends on how good your optimizer is and the compiler settings you use.

Of course you could always use macros that call functions rather than contain large inline sections of code. That is totally down to your choice.

AnthonyLambert
  • 8,768
  • 4
  • 37
  • 72