Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fuzzer failure in fuzz_bounds #7810

Open
steven-johnson opened this issue Aug 28, 2023 · 2 comments · May be fixed by #7814
Open

Fuzzer failure in fuzz_bounds #7810

steven-johnson opened this issue Aug 28, 2023 · 2 comments · May be fixed by #7814
Assignees

Comments

@steven-johnson
Copy link
Contributor

testcase-4722946583101440.zip

Running fuzz_bounds on the enclosed file produces a failure (note that this test emits the scope dump for failures):

$ ./build/linux-x64-fuzzer/test/fuzz/fuzz_bounds testcase-4722946583101440
can't prove upper bound: (0 <= -2147483648)
a = (uint16)0
b = (uint16)0
c = (uint16)0
d = (uint16)0
e = (uint16)0
select(int32((uint16)c) >= int32((uint16)c), int32x2(ramp(uint32((uint16)a), (uint32)2147483648, 2)), x2(-128))
[0, -2147483648]
In vector lane 0:
int32((uint16)a) -> 0
scope {
	a : [(uint16)0, (uint16)0]
	b : [(uint16)0, (uint16)0]
	c : [(uint16)0, (uint16)0]
	d : [(uint16)0, (uint16)0]
	e : [(uint16)0, (uint16)0]
}
@steven-johnson
Copy link
Contributor Author

Initially assigning to @abadams for triage

@abadams
Copy link
Member

abadams commented Aug 28, 2023

I think this is the issue in #7807

@abadams abadams linked a pull request Aug 28, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants