https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #13 from Chris Packham <judge.packham at gmail dot com> --- (In reply to Xi Ruoyao from comment #12) > Please provide info about how libsanitizer end up building with GCC 11.3 and > MIPS64 (such a combination is not supported and libsanitizer should not be > enabled automatically with it). Original user report was https://github.com/crosstool-ng/crosstool-ng/issues/1733 In that case the user specifically enabled LIBSANITZER support so --enable-libsanitizer was passed to GCC's configure. Based on what you're saying we should gate the LIBSANITZER on the architecture and GCC version. We do that for some options but LIBSANITZER is just enabled or disabled. We should probably also have LIBSANITZER tristate so we can let GCC decide to enable it if the stars align.
