On 2020-09-11 11:11:47 +0000, Kyryl Melekhin wrote: > If this is undefined behavior, then this line is straight up also UB. > https://repo.or.cz/tinycc.git/blobdiff/55f8963dfab5c543f7f34589d3ef9d3f2da3db14..310e3b428cfd181b51723276e6563b90d670da06:/tccgen.c > And because that line is UB, then it causes even more bugs down the drain. > At least if the output for this UB matches what other compilers generate > some bugs can be eliminated.
Note that the output of some compilers may depend on the context and optimizations. IIRC, there was a bug in PARI with such a conversion. > But what gets me the most is why doesn't gcc or clang compiler warn > on any of this. Yes, surprising. > Also how come we can't represent a 32 bit float in a 64 bit number? > On x86_64 we sure can. This depends on the value. With a large exponent, the value will not be representable. > Then you are citing ISO 17 while we don't even have full support for > C11. I have cited the latest version to mean that this has not changed. This has been like in previous versions of the standard too. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
