Posts: 62
Threads: 0
Joined: Dec 2004
JIT: You translate the code which is normaly in an intermedieate languages to native machine code on the machine the program is supposed to run on. So you can compile just for that machine.
JIT doesn't specify when this compilation happens. So there could be JITs that compile the whole application just before its execution.
I know that current JIT-compilers don't do it this way, but it is possible.
Posts: 4,307
Threads: 63
Joined: May 2003
plus platform independence is gaining more importance. So you can expect to see lesser people knowing actual assembly BUT assembly wont die
Posts: 691
Threads: 5
Joined: Apr 2002
Quote:JIT: You translate the code which normaly in an intermedieate languages to native machine code on the machine the code is supposed to run on. So you can compile just for that machine.
Correct, but you said this:
Quote:Think about JIT-compilers. They can optimize the code for the platform you run the program on. Hand written assembler can't.
Which implies that JIT compilers are designed for optimisation, which isnt necessarily true, further more JIT compilers are typically used with byte-code languages designed with the "write once, run anywhere" philosophy, in which case assembly code cannot be used at all. Most compilers generate code for a specific machine, so I can write a program in portable C code and use a C compiler to optomise it for a wide number of platforms.
Assembly code is traditionally used to optomise bottlenecks or parts of code where the compiler was unable generate highly optomised code.
esus saves.... Passes to Moses, shoots, he scores!
