> "Kevin Spencer" wrote:
>> "Ole Nielsby" wrote:
>>> Andrew Jenssen wrote:
>>>> In these Visual Studio newsgroups, is the standard
>>>> terminology to refer to the "build" process as "compilation"?
>>>> If so, what does the Just-in-Time Compiler do at runtime?
>>>> Is it to assemble the MSIL code? If so, why isn't it called a
>>>> Just-in-Time Assembler?
>>>
>>> An assembler transforms human-readable mnemonics and
>>> labels into instruction codes and addresses with little or
>>> no optimization.
>>>
>>> The Just-in-Time Compiler (or whatever they call it)
>>> compiles processor-neutral IL bytecodes (which aren't
>>> human-readable unless you disassemble them) to processor
>>> instructions and jump tables, using optimization strategies
>>> such as inlining, loop unrolling, rearranging instructions for
>>> optimal use of the processor, etc., which is traditionally a
>>> compiler job.
>>
>> It is also important to note that the word "compile" is a reference
>> to more than one process, or step, in terms of compilation. For
>> example, in applications written prior to the .Net framework,
>> developer code was first compiled into an object file of Assembler
>> code, and compiled from that into native machine code. The
>> .Net Framework performs a similar type of process. The IDE
>> compiles the developer code into MSIL, and stops. The JIT
>> compiler compiles the MSIL into native machine code at run-time.
>>
>> Kevin Spencer
>> Microsoft MVP
>> .Net Developer
>
> Then what is in the DLLs of the .NET Framework Class Library?
> Is it MSIL code that is also processed by the JIT compiler?
>
> Jenssey

"Kevin Spencer" wrote:
> "Ole Nielsby" wrote:
>> Andrew Jenssen wrote:
>>> In these Visual Studio newsgroups, is the standard
>>> terminology to refer to the "build" process as "compilation"?
>>> If so, what does the Just-in-Time Compiler do at runtime?
>>> Is it to assemble the MSIL code? If so, why isn't it called a
>>> Just-in-Time Assembler?
>>
>> An assembler transforms human-readable mnemonics and
>> labels into instruction codes and addresses with little or
>> no optimization.
>>
>> The Just-in-Time Compiler (or whatever they call it)
>> compiles processor-neutral IL bytecodes (which aren't
>> human-readable unless you disassemble them) to processor
>> instructions and jump tables, using optimization strategies
>> such as inlining, loop unrolling, rearranging instructions for
>> optimal use of the processor, etc., which is traditionally a
>> compiler job.
>
> It is also important to note that the word "compile" is a reference
> to more than one process, or step, in terms of compilation. For
> example, in applications written prior to the .Net framework,
> developer code was first compiled into an object file of Assembler
> code, and compiled from that into native machine code. The
> .Net Framework performs a similar type of process. The IDE
> compiles the developer code into MSIL, and stops. The JIT
> compiler compiles the MSIL into native machine code at run-time.
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer

"Carlos J. Quintero [VB MVP]" wrote:
> "Andrew Jenssen" wrote:
>> "Kevin Spencer" wrote:
>>> "Ole Nielsby" wrote:
>>>> Andrew Jenssen wrote:
>>>>> In these Visual Studio newsgroups, is the standard
>>>>> terminology to refer to the "build" process as "compilation"?
>>>>> If so, what does the Just-in-Time Compiler do at runtime?
>>>>> Is it to assemble the MSIL code? If so, why isn't it called a
>>>>> Just-in-Time Assembler?
>>>>
>>>> An assembler transforms human-readable mnemonics and
>>>> labels into instruction codes and addresses with little or
>>>> no optimization.
>>>>
>>>> The Just-in-Time Compiler (or whatever they call it)
>>>> compiles processor-neutral IL bytecodes (which aren't
>>>> human-readable unless you disassemble them) to processor
>>>> instructions and jump tables, using optimization strategies
>>>> such as inlining, loop unrolling, rearranging instructions for
>>>> optimal use of the processor, etc., which is traditionally a
>>>> compiler job.
>>>
>>> It is also important to note that the word "compile" is a reference
>>> to more than one process, or step, in terms of compilation. For
>>> example, in applications written prior to the .Net framework,
>>> developer code was first compiled into an object file of Assembler
>>> code, and compiled from that into native machine code. The
>>> .Net Framework performs a similar type of process. The IDE
>>> compiles the developer code into MSIL, and stops. The JIT
>>> compiler compiles the MSIL into native machine code at run-time.
>>>
>>> Kevin Spencer
>>> Microsoft MVP
>>> .Net Developer
>>
>> Then what is in the DLLs of the .NET Framework Class Library?
>> Is it MSIL code that is also processed by the JIT compiler?
>>
>> Jenssey
>>
>
> Yes, but some of them are compiled also to native x86 using NGEN.
> You can see the values "MSIL" or "x86" in a column of the GAC
> (C:\Windows\assembly folder)
>
> Carlos J. Quintero

"Ole Nielsby" <ole.nielsby@snailmail.dk> wrote in message
news:uTlELft2FHA.2816@tk2msftngp13.phx.gbl...
>
> Andrew Jenssen <AJens@YahooMail.com> wrote:
>> In these Visual Studio newsgroups, is the standard
>> terminology to refer to the "build" process as "compilation"?
>> If so, what does the Just-in-Time Compiler do at runtime?
>> Is it to assemble the MSIL code? If so, why isn't it called a
>> Just-in-Time Assembler?
>
> An assembler transforms human-readable mnemonics and
> labels into instruction codes and addresses with little or
> no optimization.
>
> The Just-in-Time Compiler (or whatever they call it)
> compiles processor-neutral IL bytecodes (which aren't
> human-readable unless you disassemble them) to processor
> instructions and jump tables, using optimization strategies
> such as inlining, loop unrolling, rearranging instructions for
> optimal use of the processor, etc., which is traditionally a
> compiler job.
>
>

Andrew Jenssen <AJens@YahooMail.com> wrote:
> In these Visual Studio newsgroups, is the standard
> terminology to refer to the "build" process as "compilation"?
> If so, what does the Just-in-Time Compiler do at runtime?
> Is it to assemble the MSIL code? If so, why isn't it called a
> Just-in-Time Assembler?

> In these Visual Studio newsgroups, is the standard
> terminology to refer to the "build" process as "compilation"?
> If so, what does the Just-in-Time Compiler do at runtime?
> Is it to assemble the MSIL code? If so, why isn't it called a
> Just-in-Time Assembler?
>
> Jenssey