-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
can't profile nim compiler #10106
Labels
Comments
timotheecour
changed the title
can't profile nim compiler
can't profile nim compiler (unless -d:release is passed)
Dec 27, 2018
timotheecour
changed the title
can't profile nim compiler (unless -d:release is passed)
can't profile nim compiler
Dec 27, 2018
But |
fix: see PR #10119 |
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Dec 30, 2018
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Dec 30, 2018
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Jan 9, 2019
Use valgrind or vtune to profile instead, both of which work like a charm! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
profiling nim compiler is an important thing, so we can find and improve compile time performance bottlenecks, but right now doesn't work:
likewith with -d:nimCallDepthLimit=32767 (using int16.high ; impossilbe to go higher)
note
EDIT: if I add
-d:release
, it succeeds, but then theprofile_results.txt
is useless:The text was updated successfully, but these errors were encountered: