https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #29 from Patrick J. LoPresti <lopresti at gmail dot com> --- (In reply to Jakub Jelinek from comment #27) > > No, that is not a reasonable fix, because it severely pessimizes common code > for a theoretical only problem. The very existence of (and interest in) this bug report means it is obviously not "a theoretical only problem". And of course Rich Felker is correct that the cost of the obvious fix is trivial and not remotely "severe". But the bottom line is that GCC is emitting library calls that invoke undefined behavior. At a minimum, GCC should document this non-standard requirement on its runtime environment. Has anyone bothered to do that? Why not?
