微软出品简洁色块型PPT.pptVIP

Adam Schaeffer Microsoft Corporation Building a High Performance 3D Games for Windows Phone SESSION CODE: WPH308 Consistent sets of hardware capabilities defined by Microsoft Windows Phone 7 Hardware Resolution Touch Input CPU / GPU RAM Hardware keyboard is optional The CPU The Evolution Of Programming Low level control Straight to the metal Raw performance tuning High level abstraction Rely on compiler and runtime Developer productivity Why C# r0x0rz Powerful and expressive Type safety reduces hard-to-track-down bugs Reflection Initializer syntax Great tooling (IntelliSense) Similar enough to C that learning and porting are easy Blazingly fast compiles C# .NET on Windows Usually within a few percent of native performance Awesome generational garbage collection Performance shootout: Raymond Chen vs. Rico Mariani /ricom/archive/2005/05/10/416151.aspx .NET on Xbox 360 360 Significant delta between managed and native .NET Compact Framework Simplistic mark-and-sweep garbage collection Xbox is not a general purpose computer Unforgiving in-order CPU architecture Requires custom VMX instructions for optimal math perf Security architecture poses challenges for jitted code .NET on Windows Phone 7 In between Windows and Xbox 360 .NET Compact Framework Keep an eye on garbage collection! ARMv7 CPU More forgiving toward jitted code ARM jitter is more mature than PPC Ways To Call Code Instance method Interface Delegate / event Reflection Virtual method Choose Your Own Address C++ allows independent choice of .NET types dictate their allocation and usage semantics Data type The memory in which a type lives (placement new) How a type instance is referenced (T, T*, T, const T) Value types int, bool, struct, Vector3 Reference types class, array, string, delegate, boxed value types A Popular Myth Oft-repeated wisdom Value types live on the stack Reference types live on the heap Value types live wherever they are declared Reference types have two piecesMemory allocated from the