[email protected] wrote: > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. > > ---1463811718-806940296-1580670508=:196090 > Content-Type: text/plain; charset=ISO-8859-15 > Content-Transfer-Encoding: 8BIT > > > Hello, > > On Sat, 8 Jun 2019, [email protected] wrote: > >> The gcc/clang folks have their heads up their asses. They've >> deliberately misinterpreted the spec claiming undefined behaviors are >> forbidden, supposedly to enable essential optimizations. Most of which >> only apply to obscure corner cases in compiler benchmark suites, that >> nobody in the real world ever benefits from. > > I realize this thread is very old, but Jeff and the C compiler folks are > right. All C programs that invoke undefined behavior are illegal C > programs and should be fixed. > > Posix threads are well-defined by Posix standards, so calling them > "undefined behaviour" is not a valid argument.
No. The POSIX spec is *not* a part of the C spec - yet it is still valid. Which simply proves the point that just because something is not defined in the C spec does not make it invalid. The compiler guys are idiots for taking this position. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
