Oh jeez... I wish I could just assume you were trolling here. Virtual memory: This is used to give every process a flat and consistent address space. It is

Oh jeez... I wish I could just assume you were trolling here. Virtual memory: This is used to give every process a flat and consistent address space. It is not just a synonym for 'swapping', and it will be around forever. String instructions: Seriously, are you just making it up as you go along? http://www.strchr.com/strcmp_and_strlen_using_sse_4.2 http://www.strchr.com/strcmp_and_strlen_using_sse_4.2 Custom opcodes: Usually done via API's that have an emulation or compatability function, DirectX, OpenGL for examples. LOCK existed: The article describes an atomic compare and write, not just a LOCK. In fact, MUTEX is implemented with the compare and exchange instruction in most OS's. http://marc.info/?t=113443157800005&r=1&w=2 http://marc.info/?t=113443157800005&r=1&w=2 I believe the no execute bit is a very recent addition to AMD64, and is not available at all on x86. Vector operations and such: Have you not heard of MMX, SSE or even graphics cards? Either I'm feeding a troll here, or you have no clues available to you.