[bugzilla-daemon@xxxxxxxxxxxxx]

Comment # 3 on bug 11009 from Peter Wu

-fsanitize=undefined seem to have a negative effect on compile times:
https://gcc.gnu.org/ml/gcc-patches/2014-05/msg01203.html

And apparently also an impact on runtime performance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44786#c1

For automated you probably want the -fno-sanitize-recover (enabled in GCC 5.0
and newer, Clang ??):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60275

Suggestion: rename --enable-asan to --enable-fsanitize, testing for address and
undefined sanitizers. Description: Enable ASAN and UBSan (longer compile times,
runtime overhead).

Later on, all kinds of sanitizers could be tested/enabled which is likely
wanted by developers to ensure quality. For more fine-grained control, one
could still drop the option and manually specify CFLAGS/CXXFLAGS/LDFLAGS or
-DCMAKE_C_FLAGS/-DCMAKE_CXX_FLAGS options.

---

      You are receiving this mail because:

• You are watching all bug changes.