Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Bernhard Urban-Forster
    @lewurm
    the changes for the managed JIT project aren't upstreamed yet, so they live in the mjit branch on lambdageek/mono
    mazegen
    @mazegen
    Anyway, this commit's message say "Drop JIT attach: use coop attach in mini, aot and interp"
    Bernhard Urban-Forster
    @lewurm
    yep, it was removed recently :smile:
    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)
    mazegen
    @mazegen
    So it was dropped because it was not compatible with coop?
    Bernhard Urban-Forster
    @lewurm
    yes
    mazegen
    @mazegen
    I'm just guessing here because the code is quite complicated :)
    Bernhard Urban-Forster
    @lewurm
    yes :disappointed:
    mazegen
    @mazegen
    Thanks again for the info, I'm going to study mini-runtime.c again soon :sweat_smile:
    juepiezhongren
    @juepiezhongren
    @lewurm can u list the main reason why bigstep is dropped, managed everything is a trend, current failure is a good lesson
    runtime components decoupling is a must
    Bernhard Urban-Forster
    @lewurm
    bigstep was done in the context of a "hack week" inside microsoft. it's a week where employees can try out new things without business justifaction
    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:
    juepiezhongren
    @juepiezhongren
    i just wonder why mstf hav not opened source midori, according to joe' articles, it seems a "bootstrapping" tech, and with the potential to bring us holy
    grail
    @joeduffy
    Bernhard Urban-Forster
    @lewurm
    as far as I know it was discontinued before MSFT jumped on the open source train
    unfortunately :disappointed:
    juepiezhongren
    @juepiezhongren
    yes
    but the code r still there, any place for our community to beg for its open source?
    Bernhard Urban-Forster
    @lewurm
    no idea :confused:
    juepiezhongren
    @juepiezhongren
    @lewurm after .net 5, will mjit be retried?
    Bernhard Urban-Forster
    @lewurm
    it has nothing to do with .net 5
    juepiezhongren
    @juepiezhongren
    i mean after,
    hahahaha
    juepiezhongren
    @juepiezhongren
    i just wander is it possible.that mstf build a managed "llvm"
    Alexander Kyte
    @alexanderkyte
    It’s not managed, but there’s a couple of other LLVM efforts https://github.com/dotnet/llilc
    Compatibility is the hard part in trying to make a new project
    juepiezhongren
    @juepiezhongren
    what is the diffs between llilc and mono' llvm part?
    Alexander Kyte
    @alexanderkyte
    They’re different VMs, with different layouts of generated runtime code and different optimization sets
    LLVM is the platform that both compile to