Related articles |
---|
Compile time of C++ vs C# shirsoft@gmail.com (Shirsoft) (2009-09-01) |
Re: Compile time of C++ vs C# marcov@stack.nl (Marco van de Voort) (2009-09-02) |
Re: Compile time of C++ vs C# DrDiettrich1@aol.com (Hans-Peter Diettrich) (2009-09-02) |
Re: Compile time of C++ vs C# cr88192@hotmail.com (BGB / cr88192) (2009-09-02) |
Re: Compile time of C++ vs C# sh006d3592@blueyonder.co.uk (Stephen Horne) (2009-09-03) |
Re: Compile time of C++ vs C# cr88192@hotmail.com (BGB / cr88192) (2009-09-03) |
Re: Compile time of C++ vs C# lefevrol@yahoo.com (Olivier Lefevre) (2009-09-04) |
From: | Olivier Lefevre <lefevrol@yahoo.com> |
Newsgroups: | comp.compilers |
Date: | Fri, 04 Sep 2009 01:41:53 +0200 |
Organization: | T-Online |
References: | 09-09-009 |
Keywords: | performance, C++ |
Posted-Date: | 05 Sep 2009 00:02:13 EDT |
You may be comparing apples to oranges. Managed languages like C# and
Java running on a VM offer two kinds of compilers: a
source-to-bytecode compiler that is called by the user and one or more
bytecode-to-native code compilers (often called JIT compilers) that
are under the control of the VM. The former (by design) perform next
to no optimizations while the latter may do so. The C++ compiler is
more akin to an optimizing JIT compiler than it is to the bytecode
compiler.
-- O.L.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.