Is there a side effect to compiling production code with gcc debugging options?

Question

For gcc flags like -coverage, do they have any side effect like performance limitation at runtime?

If not, can I just leave them in a common makefile and use them to create production code?

The Gcc document says nothing about this.

This question. How is the debugging option -g Change the binary executable?

explains -g, but what about coverage? I think yes, the added tool code should cost quite a bit at runtime

Answer 1

^{, , , .}

. , , , .

; ( , ).