https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63939
--- Comment #19 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- (In reply to howarth from comment #18) > Why are we checking in these changes in a piecemeal fashion instead of > addressing all those failing test cases listed in the "Updated patch"? I don't know what you're doing, or others are doing. I'll speak for myself. I have done a patch for "running a clean asan testsuite with llvm-virtualizer present", sent it for review, committed it, then realized I had missed one C++ testcase, then committed that as follow-up. Those fixes were about darwin mangling/wrapping some function names differently than other platforms. I now intend to do a patch for "running clean asan testsuite without llvm-virtualizer present", which is a different problem altogether: as Dominique noted, there are extra blanks in the output, so we need another adjustment to the test patterns. I did this one later, because it's orthogonal to the previous one, and also because these regexp patterns make my head hurt. Initially, I didn't see the logic in Dominique's patch (because he put the extra space in the middle of the pattern, and it confused me).
