https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107169
--- Comment #2 from Eugene Rozenfeld <erozen at microsoft dot com> --- When -gstatement-frontiers is on, the IR coming from the front end may be different with and without debug information turned on. That may cause e.g., different discriminator values and -fcompare-debug failures. See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100733. In https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f1adf45b17f7f1ed I added -gno-statement-frontiers to gcc/testsuite/c-c++-common/ubsan/pr85213.c b/gcc/testsuite/c-c++-common/ubsan/pr85213.c to work around this problem for that test.
