Summary

bitwise-not returns wrong values on non-negative arguments

Metadata

Description

The expression (bitwise-not 0) returns 4611686018427387903 (i.e. 0x3fffffffffffffff) instead of -1. The fxnot procedure does not have this problem, nor does the numbers-egg version of bitwise-not. However, (bitwise-not -1) correctly returns 0.

Changes and comments

[2017-04-21 00:21:20 UTC] evhan wrote:

5.0 doesn't exhibit this behaviour, so any fix is going to be 4.x-specific.

[2017-04-21 08:16:40 UTC] sjamaan wrote:

Looks like I haven't had my morning coffee yet ;)

[2017-04-21 08:16:40 UTC] sjamaan wrote:

1492755483150218

[2018-11-07 22:47:48 UTC] sjamaan changed milestone from someday to 4.14.0

[2018-11-07 22:47:48 UTC] sjamaan wrote:

It's only a CHICKEN 4 issue. If we ever decide to make a 4.14.0, we should tackle this. Otherwise we can just close it as wontfix, because in CHICKEN 5 it works as it should.

[2019-03-29 21:04:31 UTC] sjamaan changed status from new to closed

[2019-03-29 21:04:31 UTC] sjamaan set resolution to wontfix

[2019-03-29 21:04:31 UTC] sjamaan wrote:

Who am I kidding, there won't be a 4.14

[2019-03-29 21:05:04 UTC] sjamaan changed milestone from 4.14.0 to 5.1

[2019-03-29 21:05:04 UTC] sjamaan wrote:

Ticket retargeted after milestone deleted