https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83321
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- At least with -O0 built cc1 without valgrind checking, can't reproduce this, there are just the expected sparseset errors and nothing else. I don't see how VALGRIND_DISCARD could be optimized away, it is a volatile asm. Trying the configure you mentioned now (though on Haswell-E).
