SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Advanced Micro Devices - Moderated (AMD)
AMD 214.18-0.5%Dec 31 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: hmaly who wrote (85756)7/24/2002 10:52:26 PM
From: Joe NYCRead Replies (1) of 275872
 
Harry,

In normal business computing, widening integer registers to 64 bit will not amount to much, since hardly any integer variable need to be 64 bit (floating point variables have been 64 bit for some time already). But there are specialized cases, where 64 bit integer register is not really used for integer, but as a holder of data, and twice the data is better. For example, I don' know the best efficient method to do a string compare, but my guess is, you bring the data to the registers and do the comparison. With 64 bit, it could be done 4 byte chunks at the time, or in the bloated Unicode world, 2 2 byte characters at the time. (I haven't done any assembly programming since college, so if there is a different way to do this, I apologize. Doesn't x86 have some string compare instructions? My guess is that they still get converted by microcode to do what I just outlined).

A tiny bit of a performance benefit will come from these special cases, but mainly from doubling the number integer registers (in addition to doubling their size), which helps IPC a lot. Doubling the number of registers cuts down on number of trips to L1, L2 or memory.

Joe
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext