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

Remove JIT log file #972

Merged
merged 12 commits into from Sep 30, 2018
Merged

Remove JIT log file #972

merged 12 commits into from Sep 30, 2018

Conversation

bdw
Copy link
Contributor

@bdw bdw commented Sep 27, 2018

Using the new spesh graph comments, let's get rid of the adhoc JIT log.

timo and others added 12 commits September 27, 2018 11:19
now comments can be added by the jit and still
end up in the spesh log. Currently it outputs what
instructions bail the jit, which end the exprjit
compiler in the middle of a BB, what repr ops get
devirtualized or not.
which is almost exclusively "begin of exprjit"
comments, but still.
So that we may profile (on linux) and have insight on the time spent
on JIT-compiled frames.

Not sure if it will give good results, because we don't always compile
with -fno-omit-frame-pointer.
No need to have a separate JIT log, if we can attach messages to the
spesh debug log.
No longer necessary in jit log now that spesh graph comments exist
DynASM not being able to link is a JIT compiler error. JIT unable
to get rx pages is a configuration error (at the best of times). Both
warrant some level of noise.
We don't support it, don't need it (yet), so remove dead code
Now that we have most useful JIT information in the spesh log, we can
remove the noise from the JIT log that just replicates that.
If MVM_JIT_DEBUG is enabled, JIT specific (structured) debugging
information will be logged in the spesh log.
This is easier for the developer because tile log and expression tree
are close together.
No need to specify the exact bytecode directory, if we can put it in a
consistent place anyway.
@bdw bdw requested a review from timo September 27, 2018 14:43
@bdw bdw self-assigned this Sep 27, 2018
@lizmat
Copy link
Contributor

lizmat commented Sep 27, 2018

So, how would one find out which blocks are not getting JITted?

@jnthn
Copy link
Member

jnthn commented Sep 27, 2018

@lizmat The information is now folded into the specialization log.

@bdw bdw merged commit adef080 into master Sep 30, 2018
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

Successfully merging this pull request may close these issues.

None yet

4 participants