osmo-trx: Use gcc attribute no_sanitize to run fine with ASan enabled
So far we don't enable ASan during osmo-trx build because it adds too much overhead and makes it wrong incorrectly (too slow).
zecke informed that there's a gcc compile-time attribute to flag specific functions to be not covered by ASan. So we can run perf on osmo-trx, see the most CPU intensive functions and disable ASan on those.
#1 Updated by pespin about 2 months ago
Since we usually compile with "-fsanitize=address -fsanitize=undefined" in osmocom projects, we should probably use flags:
I need to check what happens if compiled with a compiler which doesn't support those flags. Do we need to put it into some OSMO_SANITIZE_AVOID define which is set to empty based on compiler support?