Displaying 7 results from an estimated 7 matches for "mcjitstat".
Did you mean:
mcjitstate
2010 Nov 15
8
[LLVMdev] MC-JIT Design
...) - We make a new MCJITStreamer which communicates with
the JIT engine to arrange to plop code in the right place and update
various state information.
This is the most obvious approach, is roughly similar to the way the
existing JIT works, and this is the way the proposed MC-JIT patches
work (see MCJITState object).
It also happens to not be the approach I want to take. :)
#2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
around representing everything that "can be run" on a target platform.
This is very connected to the inherent capabilities of the hardware /...
2010 Nov 15
0
[LLVMdev] MC-JIT Design
...er which communicates with
> the JIT engine to arrange to plop code in the right place and update
> various state information.
>
> This is the most obvious approach, is roughly similar to the way the
> existing JIT works, and this is the way the proposed MC-JIT patches
> work (see MCJITState object).
>
> It also happens to not be the approach I want to take. :)
>
>
> #2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
> around representing everything that "can be run" on a target platform.
> This is very connected to the inherent...
2010 Nov 16
0
[LLVMdev] MC-JIT Design
...er which communicates with
> the JIT engine to arrange to plop code in the right place and update
> various state information.
>
> This is the most obvious approach, is roughly similar to the way the
> existing JIT works, and this is the way the proposed MC-JIT patches
> work (see MCJITState object).
>
> It also happens to not be the approach I want to take. :)
>
>
> #2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
> around representing everything that "can be run" on a target platform.
> This is very connected to the inherent...
2010 Nov 15
2
[LLVMdev] MC-JIT Design
...; > the JIT engine to arrange to plop code in the right place and update
> > various state information.
> >
> > This is the most obvious approach, is roughly similar to the way the
> > existing JIT works, and this is the way the proposed MC-JIT patches
> > work (see MCJITState object).
> >
> > It also happens to not be the approach I want to take. :)
> >
> >
> > #2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
> > around representing everything that "can be run" on a target
> > platform. Thi...
2010 Nov 15
1
[LLVMdev] MC-JIT Design
...t; the JIT engine to arrange to plop code in the right place and update
> > various state information.
> >
> > This is the most obvious approach, is roughly similar to the way the
> > existing JIT works, and this is the way the proposed MC-JIT patches
> > work (see MCJITState object).
> >
> > It also happens to not be the approach I want to take. :)
> >
> >
> > #2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
> > around representing everything that "can be run" on a target platform.
> >...
2010 Nov 16
2
[LLVMdev] MC-JIT Design
...; > the JIT engine to arrange to plop code in the right place and update
> > various state information.
> >
> > This is the most obvious approach, is roughly similar to the way the
> > existing JIT works, and this is the way the proposed MC-JIT patches
> > work (see MCJITState object).
> >
> > It also happens to not be the approach I want to take. :)
> >
> >
> > #2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
> > around representing everything that "can be run" on a target platform.
> > Thi...
2010 Nov 16
0
[LLVMdev] MC-JIT Design
...e to arrange to plop code in the right place and update
>> > various state information.
>> >
>> > This is the most obvious approach, is roughly similar to the way the
>> > existing JIT works, and this is the way the proposed MC-JIT patches
>> > work (see MCJITState object).
>> >
>> > It also happens to not be the approach I want to take. :)
>> >
>> >
>> > #2 (aka FOOJIT) - MC grows a new "pure" backend, which is designed
>> > around representing everything that "can be run" on a target...