Update README.md.

Correct minor typographical & grammatical errors.
Corrected some very minor typographical errors (2), added punctuation (1 spot), added the word "the" in one spot, and changed "One Core" to "OneCore" to match the term used by Gabe Aul in his January 13, 2016 blog post.  https://blogs.windows.com/windowsexperience/2016/01/13/announcing-windows-10-insider-preview-build-11099/.
Added setenv script for Win32 platforms.
Required LLVM version updated to 3.8.1.
Minor script fixes: grammatics and default LLVM version updated.
update .gitignore.

Author: lt72

.gitignore

@@ -257,3 +257,4 @@ Zelig/Zelig/CompileTime/Llvm.NET/Win32/RelWithDebInfo/Llvm.NET.dll
 *.opendb
 /Zelig/Zelig/CompileTime/Llvm.NET/LibLLVM/generatedversioninfo.h
 /LlilumSDK/LlilumSDK/FrameworkList.xml
+Zelig/Zelig/Zelig.VC.db

README.md

@@ -4,34 +4,53 @@ Welcome to LLILUM!
 A development platform for IL based languages and UWP applications targeting Cortex-M processors.
 
 ## Why LLILUM 
-Cortex-M processors are heavily resource contrained, and yet, because of their low power consumption and optimized interrupt dispatching, are arguably the most suitable solution for IoT applications.
+Cortex-M processors are heavily resource constrained, and yet, because of their low power consumption and optimized interrupt dispatching, are arguably the most suitable solution for IoT applications.
 Existing development platfoms and tool chains that target this space are based on C/C++, and no native support for higher level languages and RAD environment exist that can take advantage of what a Cortex-M HW can offer. 
 Previous efforts in this space include [.NET Micro Framework](https://github.com/NETMF/netmf-interpreter) and other Java solutions, which are sometimes too large in code size, too slow or too difficult to extend for mainstream adoption. 
 LLILUM implements a scalable alternative to C/C++ that features comparable code size and speed, as well as easy extensibility from within the Visual Studio development tool chain. 
 
 ## What is LLILUM 
-LLILUM is an optimizing compilation tool chain that, just like .NET Micro Framework, is entirely based on [CLI](http://www.ecma-international.org/publications/standards/Ecma-335.htm). 
-LLILUM relies on the well known development experience in Visual Studio to transform source code into MSIL, and then into an intermediate represenation (IR) that is optmized for size and speed, taking into account the target platform constraints, such as memory layout, native ISA, calling convention, and, first and foremost, the application requirements. The method and type closure is optimized based on application usage of system facilities, and the type system is morphed to shrink into the smallest possible footprint. 
+LLILUM is an optimizing compiler tool chain based on the latest  [CLI](http://www.ecma-international.org/publications/standards/Ecma-335.htm) standard and [LLVM](http://llvm.org/) version [3.8.1](http://llvm.org/releases/download.html#3.8.1). 
+LLILUM relies on the compelling development experience of Visual Studio to transform source code into MSIL, and then into an intermediate represenation (IR) that is optmized for size and speed, taking into account the target platform constraints, such as memory layout, native ISA, calling convention, and, first and foremost, the application requirements. The method and type closure is optimized based on application usage of system facilities, and the type system is morphed to shrink into the smallest possible footprint. Debugging is carried out through Visual Studio and GDB.
 Standard features of CLI environments, e.g. type system (TS) introspection, garbage collection (GC) and a full featured multi-threaded execution engine (MTEE) are provided. 
 
-## State of the Art 
-LLILUM can generate runnable images for ARMv4 and ARMv5 ISA, with partial FP support. We could extend the code generator to support ARMv7-M but we decided to leverage LLVM instead, hoping we can get a wider set of targets over time. The current incarnation of the system successfully uses LLVM to target a Cortex-M ISA with a fully functional Type System. LLILUM provides GC through reference counting and full suport for MTEE. Boehm GC is in the works. 
+
+# State of the Art 
+LLILUM can generate runnable images for ARMv4 and ARMv5 ISA, with partial FP support. We could have extended the code generator to support ARMv7-M but we decided to leverage LLVM instead, hoping we can get a wider set of targets over time. 
+The current incarnation of the system successfully uses LLVM to target: 
+* Cortex-M0/3/4 ISA with 
+* A fully functional Managed Type System and FP support 
+* A reference counting collector
+* A conservative tracing collector (Bohem GC) 
+* A fully multi-threaded execution environment compatible with Cortex-M architecture for `NVIC` and `SysTick` standard controllers 
+* [lwIP](http://savannah.nongnu.org/projects/lwip/) TCP/IP stack
+* [CMSIS-RTOS](http://www.keil.com/pack/doc/cmsis/RTOS/html/index.html) porting layer for easy network stack porting 
+* Visual Studio SDK with GDB debugging 
+
+# Supported Hardware
+LLILUM supports a significant number of development boards from the [mBed](https://www.mbed.com/en/) ecosystem, and specifically: 
+* [Freescale K64F-FRDM](https://developer.mbed.org/platforms/FRDM-K64F/) Cortex-M4 development board
+* [NXP LPC1768](https://developer.mbed.org/platforms/mbed-LPC1768/) Cortex-M3 development board
+* [STMicroelectronics STM32F091RC](https://developer.mbed.org/platforms/ST-Nucleo-F091RC/) Cortex-M0 development board
+* [STMicroelectronics STM32F401RE](https://developer.mbed.org/platforms/ST-Nucleo-F401RE/) Cortex-M3 development board
+* [STMicroelectronics STM32F411RE](https://developer.mbed.org/platforms/ST-Nucleo-F411RE/) Cortex-M4 development board
+* [STMicroelectronics STM32L152RE](https://developer.mbed.org/platforms/ST-Nucleo-L152RE/) Cortex-M3 development board
 
 # Supported Languages 
-Currrent target language is C#; extensions to Python and possibly TypeScript are in the works. We are also targeting [UWP](https://msdn.microsoft.com/en-us/library/dn894631.aspx) app development, so that it will be possible to share code between a Windows 10 device app and a Cortex-M micro processor. Welcome to One Core!
+Currrent target language is C#; extensions to Python and possibly TypeScript are in the works. We are also targeting [UWP](https://msdn.microsoft.com/en-us/library/dn894631.aspx) app development, so that it will be possible to share code between a Windows 10 device app and a Cortex-M micro processor. Welcome to OneCore!
 
 # Further reading
 Please see the following documents in our wiki:
+Welcome to the _llilum_ wiki! 
 
-1. [Detailed system description](https://github.com/NETMF/llilum-pr/wiki/system) 
-  1. [Build System](https://github.com/NETMF/llilum-pr/wiki/system.build)
-  2. [Front End Configuration](https://github.com/NETMF/llilum-pr/wiki/system.frontend)
-2. [Repo layout](https://github.com/NETMF/llilum-pr/wiki/docs/resources/repo) 
-3. [Setup and build instruction](https://github.com/NETMF/llilum-pr/wiki/setup)
-4. [Build and run test demo](https://github.com/NETMF/llilum-pr/wiki/demo)
-5. [Performance considerations](https://github.com/NETMF/llilum-pr/wiki/perf)
-6. [Next steps](https://github.com/NETMF/llilum-pr/wiki/roadmap) 
+1. [Detailed system description](https://github.com/NETMF/llilum-pr/wiki/System) 
+  1. [Build System](https://github.com/NETMF/llilum-pr/wiki/Building)
+  2. [Front End Configuration](https://github.com/NETMF/llilum-pr/wiki/LLILUM-Compiler-Frontend)
+2. [Setup and build instruction](https://github.com/NETMF/llilum-pr/wiki/Setup)
+3. [Build and run test demo](https://github.com/NETMF/llilum-pr/wiki/Demo)
+4. [Performance considerations](https://github.com/NETMF/llilum-pr/wiki/Performance-Considerations)
+5. [Next steps](https://github.com/NETMF/llilum-pr/wiki/Prototype-Roadmap) 
 
 
-# Acknowledgment
+# Acknowledgments
 A big thanks to Miguel Perez Martinez for helping bringing up this proof of concepts with exceptional dedication, perseverance and competency. An even bigger thanks to D.M., who created the vast majority of this codebase single-handedly. 

Zelig/Zelig/CompileTime/Llvm.NET/LibLLVM/BuildLlvmWithVS.cmd

@@ -14,7 +14,7 @@ set LLVM_ROOT=%~d0%~p0
 set GENERATE=1
 set BUILD=1
 set REGISTER=1
-set LlvmVersion=3.8.0
+set LlvmVersion=3.8.1
 
 @REM - Allow overriding default version and disabling any of the stages via parameters
 :arg_loop
@@ -66,7 +66,7 @@ if %BUILD%==1 (
 if %REGISTER%==1 (
     @echo registering LLVM path in registry
     reg add HKCU\Software\LLVM\%LlvmVersion% /v SrcRoot /d %LLVM_ROOT% /f
-    echo Setting per machine rigistry path
+    echo Setting per machine registry path
     echo NOTE: Administrator permissions required to set per machine registry settings.
     echo       If you get 'ERROR: Access is denied.' the per machine registration is not available
     reg add HKLM\Software\LLVM\%LlvmVersion% /v SrcRoot /d %LLVM_ROOT% /f
@@ -90,7 +90,7 @@ goto :exit
 @echo     -g- disables the cmake project generation phase
 @echo     -b- disables the code build phase 
 @echo     -r- disables the registry update
-@echo     -v ^<LlvmVersion^> sets the LLVM version number used for the registry entry (Default is 3.7.0)
+@echo     -v ^<LlvmVersion^> sets the LLVM version number used for the registry entry (Default is 3.8.1)
 @echo.
 @echo The registry entry is used by the LlvmApplication.props Propertysheet for VC projects to locate the various
 @echo LLVM headers and libs. Alternatively, if LLVM_SRCROOT_DIR is provided either as an environment variable

Zelig/Zelig/CompileTime/Llvm.NET/LibLLVM/LlvmApplication.props

@@ -9,7 +9,7 @@
         -->
     <LlvmVersionMajor Condition="'$(LlvmVersionMajor)'==''">3</LlvmVersionMajor>
     <llvmVersionMinor Condition="'$(llvmVersionMinor)'==''">8</llvmVersionMinor>
-    <LlvmVersionBuild Condition="'$(LlvmVersionBuild)'==''">0</LlvmVersionBuild>
+    <LlvmVersionBuild Condition="'$(LlvmVersionBuild)'==''">1</LlvmVersionBuild>
     <LLVM_VERSION Condition="'$(LLVM_VERSION)'==''">$(LlvmVersionMajor).$(llvmVersionMinor).$(LlvmVersionBuild)</LLVM_VERSION>
     <!-- Source ROOT Dir contains the full source of LLVM. To support both developer and automated build service
              scenarios try user registry, then HKLM-64 and HKLM-32 in that order

setenv32.cmd

@@ -0,0 +1,23 @@
+@echo off
+
+set LLILUM_ROOT=%~dp0%
+
+prompt $_$+---$G $P$_$+   $G$_Cmd$G
+
+::
+:: Set LLVM environment variables.
+::
+
+set LLVM_BIN=%LLVM_SRCROOT_DIR%\build\Win32\Release\bin\
+set LLVM_INCLUDE=%LLVM_SRCROOT_DIR%\include\
+set LLVM_LIBS=%LLVM_SRCROOT_DIR%\
+
+::
+:: Add pyOCD and and make to path.
+::
+
+set PATH=%LLILUM_ROOT%Zelig\tools;%LLILUM_ROOT%Zelig\tools\openocd\bin-x64;%PATH%
+set LLILUM_OPENOCD_SCRIPTS=%LLILUM_ROOT%Zelig\tools\openocd\scripts\
+
+cd Zelig
+echo Welcome to LLILUM!