incorrect XOR operation #1552

New issue

Open

opened 2025-12-28 17:16:49 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:16:49 +00:00

Owner

Originally created by @Turalchik on GitHub (Aug 29, 2025).

func TestXORByte(t *testing.T) {
	src := `
		package foo
		func Main() byte {
			return ^byte(0)
		}
	`
	eval(t, src, big.NewInt(255))
}

Current Behavior

The function returns -1.

Expected Behavior

The function should return 255.

Steps to Reproduce

Reproduce the test above.

Your Environment

v0.111.0

Originally created by @Turalchik on GitHub (Aug 29, 2025). ```go func TestXORByte(t *testing.T) { src := ` package foo func Main() byte { return ^byte(0) } ` eval(t, src, big.NewInt(255)) } ``` ## Current Behavior The function returns -1. ## Expected Behavior The function should return 255. ## Steps to Reproduce Reproduce the test above. ## Your Environment v0.111.0

sami added the

bug

compiler

labels

2025-12-28 17:16:49 +00:00

sami commented

2025-12-28 17:16:50 +00:00

Author

Owner

@roman-khimov commented on GitHub (Aug 31, 2025):

There are no proper int types in VM and in our Go compiler, byte/int/int16/uint64/etc are all the same int256 effectively. At this stage this is the expected behavior.

@roman-khimov commented on GitHub (Aug 31, 2025): There are no proper int types in VM and in our Go compiler, byte/int/int16/uint64/etc are all the same int256 effectively. At this stage this is the expected behavior.