Federico Bruni writes:
In fact, lilypond is another package affected: https://bugzilla.redhat.com/show_bug.cgi?id=1568274 http://lists.gnu.org/archive/html/lilypond-user/2018-05/msg00081.html
It's been my experience, over the last decade, or so, that each successive major gcc release has had much less tolerance for undefined behavior. And that the correct approach is to fix the undefined behavior. So, if lilypond is triggering undefined behavior, then that's what needs to be fixed, not gcc.
pgpQKLcWQTfew.pgp
Description: PGP signature
_______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected]
