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

match has poor compile-time performance #76

Open
pbackus opened this issue Oct 28, 2021 · 1 comment
Open

match has poor compile-time performance #76

pbackus opened this issue Oct 28, 2021 · 1 comment

Comments

@pbackus
Copy link
Owner

pbackus commented Oct 28, 2021

See this thread on the D forum:

https://forum.dlang.org/post/[email protected]

Profiling the test suite with LDC's --ftime-trace flag should be the first step here. Additional test cases, especially those derived from real-world code, would be very helpful for this.

@pbackus
Copy link
Owner Author

pbackus commented Feb 17, 2022

Looks like --ftime-trace isn't fine-grained enough for this. Next step is runtime profiling of the D compiler, to see exactly where in semantic analysis it's spending its time.

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

1 participant