I don't care about cool, nor do I have any urge to separate jet if
it's not separable.
That said, I care about portability.
How hard will it be to port jet and opt to a new chip - say PPC?
geir
Egor Pasko wrote:
Refactoring Pros:
* more logical structure, looking cool
Refactoring Cons:
*
On the 0x21C day of Apache Harmony Geir Magnusson, Jr. wrote:
I don't care about cool, nor do I have any urge to separate jet if
it's not separable.
That said, I care about portability.
How hard will it be to port jet and opt to a new chip - say PPC?
Experience shows that JET is much
On 11/7/06, Xiao-Feng Li [EMAIL PROTECTED] wrote:
Agreed. Without the explanation of JET as only a fast path, I also
thought JET and OPT are two different JITs. And actually as I can
recall, JET and OPT are indeed treated as two different JITs that the
EM can select in the JITs chain.
Ok, thanks for the info. :-) -xiaofeng
On 11/7/06, Mikhail Fursov [EMAIL PROTECTED] wrote:
On 11/7/06, Xiao-Feng Li [EMAIL PROTECTED] wrote:
Agreed. Without the explanation of JET as only a fast path, I also
thought JET and OPT are two different JITs. And actually as I can
recall, JET and
Alex Astapchuk wrote:
Pavel Pervov wrote:
Hello, community,
Working through DRLVM sources I (once again) looked at organization of
jitrino code.
Actually, there are two JITs hidden inside jitrino: JET and OPT.
As far as I may observe - these two are code-independent from each other.
Geir Magnusson Jr. wrote:
Alex Astapchuk wrote:
Pavel Pervov wrote:
Hello, community,
Working through DRLVM sources I (once again) looked at organization of
jitrino code.
Actually, there are two JITs hidden inside jitrino: JET and OPT.
As far as I may observe - these two are
Jet is a startup fast compilation path, not a seperate pluggable jit. So,
while modularity and seperation are important requirements, they may not be
needed here.
Also, Mikhail and Alex are the best people to decide on this.They are
literally the two people who know this code best :-)
Jet is a startup fast compilation path, not a seperate pluggable jit. So,
while modularity and seperation are important requirements, they may not
be
needed here.
JET can work standalone (-Xem:jet specified), OPT can work standalone
(-Xem:opt), so from outside POV they are independent. Also,
Agreed. Without the explanation of JET as only a fast path, I also
thought JET and OPT are two different JITs. And actually as I can
recall, JET and OPT are indeed treated as two different JITs that the
EM can select in the JITs chain.
Honestly, different paths give me an impression that they
-1 to separating Jitrino.JET and Jitrino.OPT.
As Mikhail and Alex said, JET and OPT share their code in many areas. So, to
achieve true modularity separating them we'll need either to duplicate
shared code or externalize internal JIT interfaces. The former is
definitely bad and the latter implies
Refactoring Pros:
* more logical structure, looking cool
Refactoring Cons:
* takes time
* cool look does not help to read the code
* more interfaces, possible code duplication
* many old patches become outdated because of massive file renaming
So, I am (-1) for that kind of refactoring.
I feel
Pavel Pervov wrote:
Hello, community,
Working through DRLVM sources I (once again) looked at organization of
jitrino code.
Actually, there are two JITs hidden inside jitrino: JET and OPT.
As far as I may observe - these two are code-independent from each other.
JIT-guys, could you comment?
Hello, community,
Working through DRLVM sources I (once again) looked at organization of
jitrino code.
Actually, there are two JITs hidden inside jitrino: JET and OPT.
As far as I may observe - these two are code-independent from each other.
JIT-guys, could you comment?
If I'm right here I
Pavel Pervov wrote:
Hello, community,
Working through DRLVM sources I (once again) looked at organization of
jitrino code.
Actually, there are two JITs hidden inside jitrino: JET and OPT.
As far as I may observe - these two are code-independent from each other.
JIT-guys, could you comment?
It was Class.h actually... :)
I'm afraid if I do that, those supporting JITs will come after me, and I
won't write any more to this list.
P.S. It might be not that bad from someones POV, but I would prefer staying
alive...
On 11/3/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
Pavel
On 11/3/06, Pavel Pervov [EMAIL PROTECTED] wrote:
Hello, community,
Working through DRLVM sources I (once again) looked at organization of
jitrino code.
Actually, there are two JITs hidden inside jitrino: JET and OPT.
As far as I may observe - these two are code-independent from each other.
16 matches
Mail list logo
