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

OOM in getUBPhiPaths #218

Closed
regehr opened this issue Jun 3, 2016 · 2 comments
Closed

OOM in getUBPhiPaths #218

regehr opened this issue Jun 3, 2016 · 2 comments

Comments

@regehr
Copy link
Collaborator

regehr commented Jun 3, 2016

While building current LLVM, getUBPhiPaths recurses to depth ~1000, eventually exhausting RAM on the machine I'm using. I've read the code and we already have some attempts to use less resources in this part of Souper. My current thought is that we simply permit Souper to fail (by bailing on this particular expression) when such a large depth of phi nodes is found, what do people think?

@chenyang78
Copy link
Contributor

Yes, this part was optimized for resource usage, but looks like the optimization is not good enough for building current LLVM. The approach that you proposed is fine to me.

@regehr
Copy link
Collaborator Author

regehr commented Oct 28, 2016

Fixed.

@regehr regehr closed this as completed Oct 28, 2016
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

No branches or pull requests

2 participants