this is the basic malloc optimization https://godbolt.org/g/aFuFHc pic.twitter.com/0lX2Gy3pYf
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
In other cases the whole problem was that it optimized out an always-true failure condition. Are you saying now it doesn't optimize when failure is unlikely?
GCC can remove dead malloc calls, but only if they have no out-of-memory check. Has been that way for a long time. Clang pretends the malloc call is going to succeed when removing dead stores: http://godbolt.org/g/3t9H4Y . It will do that for malloc(SIZE_MAX) too.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.