If I build with -g to get symbols, but without also using -Og (for example, in CMake nomenclature, RelWithDebInfo versus Debug), I get warnings.
But what exactly are the ABI incompatibilities that -Og will allow it to detect, which it cannot do otherwise?
I ask because the abi dump files from a full Debug build of a large library are enormous, but the ones from a RelWithDebInfo build are sufficiently smaller that it allows me to check them into the project as reference for CI checks of ABI conformance. I'd love to stick to the smaller dump files, unless by doing so I am disabling a part of the analysis that is actually important to me.
More of a question than an true issue, I suppose.
If I build with -g to get symbols, but without also using -Og (for example, in CMake nomenclature, RelWithDebInfo versus Debug), I get warnings.
But what exactly are the ABI incompatibilities that -Og will allow it to detect, which it cannot do otherwise?
I ask because the abi dump files from a full Debug build of a large library are enormous, but the ones from a RelWithDebInfo build are sufficiently smaller that it allows me to check them into the project as reference for CI checks of ABI conformance. I'd love to stick to the smaller dump files, unless by doing so I am disabling a part of the analysis that is actually important to me.