That comment was actually a considered comment: when we look at what warnings we should produce, we consider cases where everyone has written code a particular way and the fact that it isn&#x27;t defined is actually a language bug.<p>We (the Clang community members, and I suspect the GCC community members as well) have also worked to change language standards to provide guarantees relied on consistently and where the lack of guarantee has no reasonable basis. Also that comment is very old, and predates us learning about all of why this is probably something actually worth warning on. That discussion ended up in a different forum, and we do actually warn on stuff like self assignment.<p>Understand that it is often precisely the people working on a compiler that <i>do</i> deal with the cases of when we discover widespread UB in real code and whether or not the code is incorrect and must be changed or the standard is incorrect and must be fixed.<p>But all of that is about a warning, and not about the actual question of how the compiler and the system library interact.<p>Note that both Clang and GCC have at least some variants of this bug, and so I don&#x27;t actually expect glibc to break this in the foreseeable future. But we&#x27;re still actively working to defend against this on platforms for which we don&#x27;t have a guarantee.