https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
--- Comment #14 from Martin Jambor <jamborm at gcc dot gnu.org> --- This issue is still present and unfortunately it is the kind of bug that either creates manual periodic work because people need to go over logs to verify that no new other UBSAN failure has appeared or it effectively prevents those new failures from being discovered quickly because "UBSAN is known to be red" (which I believe has happened because I do not see an issue filed for a failure at fortran/trans-expr.cc). Is this really a difficult issue to fix? Could it get a bit more priority, please?
