Perhaps I'm not skilled in git enough - is there any way how to see only all the commit related to the mjit? This branch seems to be up-to-date with mono HEAD and it is hard to find all the relevant commits for me.
For example, I'm interested in changes in method-to-ir.c
I think the easiest would be to
git diff origin/master
or use that GitHub link https://github.com/mono/mono/compare/master...lambdageek:mjit
that said, there aren't any changes to
method-to-ir.c. This file is essentially the front-end to the "Mini JIT compiler"
the main goal of this managed JIT project is to come up with an interface, so we can plug in different JIT compilers. The main changes on the runtime side are in
mini-runtime.c (yeah... the naming is... confusing)
@lewurm Hi, thanks for the help. I was confused by the MONO_CEE_MONO_JIT_ATTACH that was dropped later. I'm asking about
method-to-ir.c because I know a little about the mini jit, in contrast to LLVM jit. I will dive into mini-runtime.cnow to get more familiar with the whole process.
@mazegen:
MONO_CEE_MONO_JIT_ATTACH is another good example of "misleading names" :sweat_smile: JIT in that context means a thread that runs managed code (with the JIT). these days the JIT could be AOT'd code or the interpreter... so the name of this opcode should really be MONO_CEE_MONO_MANAGED_THREAD_ATTACH :smile:
@lewurm Yes, and speaking about this one, I found one commit by @lambdageek that doesn't show up in the commits listed by the GitHub link you posted earlier, I'm not sure why: https://github.com/lambdageek/mono/commit/766dacef2240ac046723e80aaba2cfbbf9caad90#diff-e7526071878d708680e4a8c5fa5a46ed
it's related to the thread suspension mechanism in mono: Previously we had a preemptive suspension (via posix signals essentially) and we gradually moving forward to a cooperative suspension mechanism (by using safepoints)
https://www.mono-project.com/docs/advanced/runtime/docs/coop-suspend/ some more information on this topic
runtime components decoupling is a must
while the idea is nice, it would take a long time to productise with little visible benefit for the end-users
we didn't necessarily drop it, it's just we don't have a time budget to work on it currently. if you are interested to work on it, your contributions are very welcome :smile:
grail
@joeduffy
unfortunately :disappointed:
but the code r still there, any place for our community to beg for its open source?
hahahaha
Compatibility is the hard part in trying to make a new project
LLVM is the platform that both compile to