-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
maximum sized integer literal (u65535) trips compiler (memory, CPU use explosion) #12116
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
Labels
Milestone
Comments
I believe this really has to do with consuming the literal; computing the same value via (wrapping) arithmetic works just fine:
|
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 15, 2022
Closes ziglang#12169 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12159 Closes ziglang#12057 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 15, 2022
Closes ziglang#12169 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12057 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 15, 2022
Closes ziglang#12169 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12057 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#11986 Closes ziglang#11995 Closes ziglang#12000
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 15, 2022
Closes ziglang#12169 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12057 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#11986 Closes ziglang#11995 Closes ziglang#12000
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 15, 2022
Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#11995 Closes ziglang#12000
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 16, 2022
Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#11995 Closes ziglang#12000
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Dec 17, 2022
Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#12051 Closes ziglang#12092 Closes ziglang#12116 Closes ziglang#12119 Closes ziglang#12142 Closes ziglang#12450 Closes ziglang#13113 Closes ziglang#11995 Closes ziglang#12000
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 28, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 29, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 29, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 29, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 29, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
May 29, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 2, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 6, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 13, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 15, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 17, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 18, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 19, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 19, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 20, 2023
wooster0
added a commit
to wooster0/zig
that referenced
this issue
Jun 27, 2023
TUSF
pushed a commit
to TUSF/zig
that referenced
this issue
May 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Zig Version
0.9.1
Steps to Reproduce
create the problematic file with these steps (sorry for including code to generate this, gh issue complains about too long body for this field)
$ cat bomb.zig
$ ones=$(head -c 65535 /dev/zero | tr '\0' '1');
$ sed -i bomb.zig -e "s;X;$ones;"
open something where you can see CPU and memory use (e.g. xosview, top, whatever)
then run the test:
zig test bomb.zig
Watch the resource usage explode.
Expected Behavior
test runs successfully
Actual Behavior
test run runs out of memory
The text was updated successfully, but these errors were encountered: