-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
regression(0.20.0 => devel): var params assignment gives silently wrong results in VM #15974
Labels
Comments
This was referenced Nov 15, 2020
Closed
same first bad commit with #12551 and similar symptom involving var param. |
capocasa
pushed a commit
to capocasa/Nim
that referenced
this issue
Mar 31, 2023
…im-lang#16780 nim-lang#16613 nim-lang#14553 nim-lang#19909 nim-lang#18641 (nim-lang#19902) [backport] * revert nim-lang#12217 since the root problem seems to have been fixed; fix nim-lang#15974;fix nim-lang#12551; fix nim-lang#19464 * fix nim-lang#16020; fix nim-lang#16780 * fix tests and nim-lang#16613 * fix nim-lang#14553 * fix nim-lang#19909; skip skipRegisterAddr * fix nim-lang#18641
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
regression(0.20.0 => devel): in VM, a copy of a var param is affected when that param is later re-assigned.
Example
Current Output
CT:
3
RT:
2
Expected Output
CT:
2
RT:
2
Additional Information
regression:
nfIsRef in regs[ra].node.flags
[AssertionError]var s: seq[Foo]
ands.add a
git bisect output
=> points to #12217 /cc @Araq
The text was updated successfully, but these errors were encountered: