It is just an abort trap. The ‘make check' also passes if turning off optimization. I would have expected UBSan to not change anything in optimization, but merely report the issues it finds. Apparently it finds nothing, so it may suggest a compiler bug.
> On 25 Oct 2019, at 22:34, David Blaikie <dblai...@gmail.com> wrote: > > Hard to know what might be happening - what sort of failure you're seeing, > etc. Perhaps UBSan is stabilizing/changing unspecified rather than undefined > behavior - or the test is failing due to some undefined behavior that UBSan > doesn't catch, etc. > _______________________________________________ cfe-users mailing list cfe-users@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users
