The best part of PDC10 is the Q&A feature in the streaming app, where the team members will answer online question while the speaker is on stage. its better than Ch9Live because more people are answering, and on more topics. I hope Build 2012 can do the same.
Alright, Charon aka Ma-Config showed me this patent, it has a detailed description of MDIL.MDIL Instruction Set: Explaining Instruction Formats and Conventions in MDIL Code
This section discusses the binary encoding and the semantics of MDIL instructions.
What is MDIL? MDIL is a lower level of intermediate language than MSIL. It gives up on the goal of machine independence—in fact the acronym MDIL stands for Machine Dependent Intermediate Language. MDIL doesn't compete with MSIL—rather, going through MDIL is another step in the compilation pipeline going from source code in languages like C#, Visual Basic®, Managed C++ via MSIL to native code (mark of Microsoft Corporation). MDIL doesn't try to abstract properties of the target processor, but it still provides a layer of insulation against versioning of both managed code and the execution engine MDIL code is compiled for.
MDIL is not directly executable. Instead, a binder reads the MDIL code and produces executable machine code from it. MDIL code is thus reminiscent of object files resulting from the compilation of unmanaged code which are run through a linker to produce final executable machine code. However, pseudo instructions in MDIL may go further than fixups in traditional object files—rather than just fixing up parts of instructions (like an address field), MDIL pseudo instructions may generate new native instructions which possibly differ in length from the pseudo instruction. Thus the MDIL binder is more complicated than a linker because the binder has to adjust the jumps in the resulting native code so they still jump to their intended targets. With this added complexity also comes added power—MDIL code can be robust against base types adding new fields or virtual methods, so it can be considered a solution to the "brittle base class problem".
OK, apparently the time is still not so 'right' yet, so let me looking at it a little more.
The word MDIL is not a new thing, we have seen it in Bartok before:
/TargetMdil=<bool> (currently False) Target MDIL rather than native code
/TargetMdilEHPerBB=<bool> (currently False) When targeting MDIL, emit separate EH records for each basic block
/TargetMdilBartokRuntime=<bool> (currently False) When targeting MDIL, assume that libraries include the Bartok runtime
/ClrMdil=<bool> (currently False) Target/consume CLR-MDIL rather than Bartok-MDIL (not complete)
/RedhawkMdil=<bool> (currently False) Target Redhawk-MDIL rather than Bartok-MDIL (currently implies ClrMdil as well)
/RedhawkBaseClassLibrary=<bool> (currently False) Generate MDIL for a Redhawk base class library (include well-known types table in the CTL)
/MdilV2=<bool> (currently False) Use version 2 of the MDIL instruction encoding (automatic/required for x64)
So there were CLR-MDIL, Bartok-MDIL and Redhawk-MDIL, and also MDIL v2, and thats many years ago.
Aug 05, 2012 at 10:59PM
The forum of channel9.msdn.com can't understand the url in msdn.microsoft.com, wtf.
What was the code name of Windows 8 again ?
@Charles: Good to hear and thank you very much !
It means my time window is narrowing, lets see how much I can do before the truth surfaces.
Sofar I saw an MDILBinder.exe inside the emulation image, and apparently there will also be an mdilnigenlibrary.dll. Plus, evey managed assembly .dll or .ni.dll has a .mdil PE section, I hope these are related to CrossGen.exe.
Also, I saw a HDRLens.mdil.xap somewhere in the vhd.
Wow, that's cool news ! Thanks !
And, according to Joe's latest blog post, Krzysztof Cwalina and Adam Nathan are also in the private incubation team now ? hmmm.... adding this to my notebook is this a sign that the TSI and DevDiv getting back on track after the Win8 push ? Ok I'm reading too much again