Den tors 17 jan. 2019 kl 14:05 skrev Mayuresh Kathe <[email protected]>: > > Don't know if this has been discussed here before, but I found the > following excerpt from the article at > http://www.yodaiken.com/2018/12/31/undefined-behavior-and-the-purpose-of-c/ > unnerving; > ... often the writers of the ISO C Standard have thrown up their hands > and labeled the effects of non-portable and potentially non-portable > operations "undefined behavior" for which they provided only a fuzzy > guideline. Unfortunately, the managers of the gcc and clang C compilers > have increasingly ignored the guideline and ignored well-established > well-understood practice, producing often bizarre and dangerous results > ... >
This came up before clang replaced gcc on certain arches: https://marc.info/?l=openbsd-misc&m=137530560232232 -- May the most significant bit of your life be positive.
