-
Notifications
You must be signed in to change notification settings - Fork 37
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
spicy-build
: High memory consumption reading files.
#1624
Comments
This is a current limitation of spicy/spicy/toolchain/bin/spicy-build Line 140 in 38b13fc
Random access is currently always enabled for all units, but removed for units which do not need it by the optimizer. Since |
It might be possible to rewrite |
We previously would emit single C++ source files from `spicy-build`. This made it impossible to enable optimizations since we could not know whether individual code was used. Since optional features are by default enabled and only disabled through an optimizer pass this meant that `spicy-build` emitted code which performed a lot of work not done usually. This patch reworks `spicy-build` to use `spicyc`'s `-x` instead which has a global view and can run optimizations, and emits all source files into a prefix. Closes #1624. Closes #1625. Closes #1622.
While processing a file (
-f
) with an executable created byspicy-build
the process' memory consumption is constantly growing up to the size of the input file. Looks like processed input is never released. Running the same parser usingspicy-driver
, the memory consumption is stable.The text was updated successfully, but these errors were encountered: