Issue 112 in cog: Literal > 16rFFFFFFFF should better be generated as unsigned long long
Status: Accepted Owner: nicolas....@gmail.com Labels: Type-Defect Priority-High
New issue 112 by nicolas....@gmail.com: Literal > 16rFFFFFFFF should better be generated as unsigned long long http://code.google.com/p/cog/issues/detail?id=112
This was one change of issue 92 which was forgotten.
Currently, gcc is kind enough to correct 0xffffffffffffffffUL by itself, but it issues a warning and that stinks like Undefined Behaviour.
Find attached correction based on .oscog-emm.241
Comment #1 on issue 112 by nicolas....@gmail.com: Literal > 16rFFFFFFFF should better be generated as unsigned long long http://code.google.com/p/cog/issues/detail?id=112
Please integrate before it rots. Note that if unsigned long has 64 bits, the ULL suffix is unecessary, but it won't arm.
Attachments: CogIssue112_unsigned_long_long_suffix.st 1.4 KB
Comment #2 on issue 112 by guillermopolito@gmail.com: Literal > 16rFFFFFFFF should better be generated as unsigned long long http://code.google.com/p/cog/issues/detail?id=112
Mirrored in https://pharo.fogbugz.com/default.asp?11378#82889
vm-dev@lists.squeakfoundation.org
-
cog＠googlecode.com