This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
As my former Sun Microsystems colleague Eric Schrock (nickname Schrock) wrote in November 2004 : "On i386, you at least had the advantage of increasing the number of usable registers by 20%. This technique saves two instructions in the prologue and epilogue and makes one additional general-purpose register (%rbp) available."
In 2004 I was working for Microsoft in the Xbox group, and a new console was being created. Back in the day I wrote a lot of benchmarks in order to look for places where the actual performance of the CPU didn’t match what we expected. I wrote a lot of benchmarks. One benchmark I wrote measured the L2 cache latency.
I became the Sun UK local specialist in performance and hardware, and as Sun transitioned from a desktop workstation company to sell high end multiprocessor servers I was helping customers find and fix scalability problems. We had specializations in hardware, operating systems, databases, graphics, etc.
ReadFile WriteFile ReadFileScatter WriteFileGather GetOverlappedResult For extended details on the 823 error, see Error message 823 may indicate hardware problems or system problems ( [link] i crosoft.com/default.aspx?scid=kb Contact your hardware manufacture for assistance.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content