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

Compilation takes a long time/forever with more specialized type #92

Closed
wyager opened this Issue Nov 2, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@wyager

wyager commented Nov 2, 2015

I was investigating some approaches for improving the simplicity of the generated verilog, and I was curious if further type specialization would result in the generation of fewer modules. See wyager/Lambda16@080ec13

For whatever reason, this change causes Cλash to have a hard time. It's either taking a very long time or not terminating at all.

I had similar problems when I removed the WriteCache arguments altogether and re-wrote the function in terms of signals, such that the WriteCaches were generated within the function instead of passed as an argument.

It seems like this only happens when I specialize the size of the caches within the same module as the cache-size-parametric functions.

@christiaanb

This comment has been minimized.

Show comment
Hide comment
@christiaanb

christiaanb Nov 2, 2015

Contributor

Thanks for the report. I'm on vacation right now, and won't be able to work on a fix until November 11.

Contributor

christiaanb commented Nov 2, 2015

Thanks for the report. I'm on vacation right now, and won't be able to work on a fix until November 11.

@wyager

This comment has been minimized.

Show comment
Hide comment
@wyager

wyager Nov 2, 2015

No problem. Should be able to work around it until then. Have fun.

wyager commented Nov 2, 2015

No problem. Should be able to work around it until then. Have fun.

@christiaanb

This comment has been minimized.

Show comment
Hide comment
@christiaanb

christiaanb Nov 11, 2015

Contributor

The current fix really feels like it is a red hearing, because I cannot really put my finger on to why the old code was causing problems. I will investigate further tomorrow.

Regardless, your code does compile now.

Contributor

christiaanb commented Nov 11, 2015

The current fix really feels like it is a red hearing, because I cannot really put my finger on to why the old code was causing problems. I will investigate further tomorrow.

Regardless, your code does compile now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment