-
Notifications
You must be signed in to change notification settings - Fork 34
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
Upgrade to purity inference #257
Conversation
…_value_def_suffixed
No need to worry about valgrind on nix, the next step is this. |
@@ -7,7 +7,7 @@ lto = true | |||
strip = "debuginfo" | |||
# You can comment this out if you hit a segmentation fault similar to the one in see issue github.com/roc-lang/roc/issues/6121 | |||
# Setting this to 1 should improve execution speed by making things easier to optimize for LLVM. | |||
codegen-units = 1 | |||
# codegen-units = 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what's going on here. I don't remember changing this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, probably should update that back to codegen-units = 1
in a follow up
# not used, leaving here for future reference if we want to run valgrind on an example | ||
# if [ "$no_ext_name" == "args" ] && command -v valgrind &> /dev/null; then | ||
# valgrind $EXAMPLES_DIR/args argument | ||
# fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving this here for future... we went to all the effort to use valgrind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Long time coming!!!
# TODO | ||
# I deleted the Arg parser as a workaround for issues it was causing when upgrading to purity inference. | ||
# The plan is for people so use Weaver or simmilar in future. We can discuss putting it back in if we still | ||
# want the "batteries included" experience, but either way that will need to be upgraded/tested with | ||
# purity-inference. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO note... I can remove this in this or follow up, I left this here for @Anton-4
No description provided.