128 bit windows 8




















We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience.

You will still see some advertising, regardless of your selection. Because we do not track you across different devices, browsers and GEMG properties, your selection will take effect only on this browser, this device and this website.

Skip to Content. About Subscribe Events. By Kurt Mackie October 9, More on this topic from GCN: Get ready for a date with Share This:. This website uses cookies to enhance user experience and to analyze performance and traffic on our website. We also share information about your use of our site with our social media, advertising and analytics partners.

Cookie Preferences Cookie List. Do Not Sell My Personal Information When you visit our website, we store cookies on your browser to collect information.

Allow All Cookies. Cookie List A cookie is a small piece of data text file that a website — when visited by a user — asks your browser to store on your device in order to remember information about you, such as your language preference or login information.

Sale of Personal Data We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience.

Social Media Cookies We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience.

Targeting Cookies We also use cookies to personalize your experience on our websites, including by determining the most relevant content and advertisements to show you, and to monitor site traffic and performance, so that we may improve our websites and your experience.

GCN uses cookies for analytics and personalization. By continuing to use this site, you agree to our use of cookies. Read our Privacy Policy to find out more. Almost There! Full Name. I Work For Please Provide Your Org. Phone Number. Zip code. Country Name. Yes, I want to receive occasional updates from partners. I agree to the use of my personal data by Government Executive Media Group and its partners to serve me targeted ads.

There is simply no compelling reason to port a working bit application to bit unless you need the additional address space or you need to do bit computations. There are of course cases where a port is needed because of the need to interface existing bit DLLs and executables i. Not only 64 bits computations, but the 64 bit mode also includes more registers available, so functions can be optimized to pass parameters through registers and not use the slow stack.

Besides, there is nothing magic about have 16 GPRs that makes it possible to use registers instead of the stack — you can use reg calling conventions with just 8 registers in bit code as well — it just depends on how many parameters you are using, their types, and how many local variables you are defining. If your code has a lot of parameters or a lot of local variables then 16 GPRs will probably help, otherwise it will not have any effect or very little effect.

Stupid comment. You could at least write something more elaborated. I meant to say most applications developed for Windows are 32 bits. In the business world there are still a lot of bit apps in active use.

My company still has a bit DOS application that is used daily as well as a few legacy applications with bit installers. These basically make a move to a bit OS an show stopper unless some form of virtualization is involved. Windows 7 is a far more likely option for us than Vista ever could be in this regard.

Due to the fact that there is a windows XP emulation system that allows for legacy applications to run. Then there would be no reason to hype it so much. Even in the filesystem space, 64 bits is enough. We already have support for bit numerical processing in the form of SSE support. I suspect this is probably an effort to prepare for bit FPU. Having full bit FPU would be useful for a variety of things, and could pave the way to eventually unifying SSE with x I also think the main motivation behind bit support is probably not the file system or addressing more memory but for native support of bit floating point numbers.

Even today, there are a number of number crunching applications which could gain some reasonable computational efficiency by using processors with native bit support. Processing of things like GUIDs and bit encryption keys may also see benefit, no? Yes, bring the power of bit floating point registers to the people! It may have nothing to do with memory size, the number of bit a processor generally refers to the maximum integer size, not the memory capacity.

That said in the past it has been used to refer to the data bus width. The 68K was called a 16 bit machine, it processed 32 bit integers it could access a 24 bit address range and had a 16 bit data bus. What was it? Just to confuse things, if you count the vector unit you are already using bit processors …and have been since the PowerPC G4! Quite possibly for use in a filing system. The vector unit would be the obvious place to add this. They have separate address spaces but with bits you can treat them as a single machine.

Given computers will almost certainly eventually go down that route, some form of bit addressing makes some sense for large machines. Your talking about software quality. That has nothing to do with bit vs bit vs bit or anything in between. Those are attributes of the underlying hardware. Some software can take advantage of increased address space, additional registers, large integers, etc. Moving from bit to bit was most definitely useful, regardless of how crappy software still tends to be.

Do we really need bit? My answer is simple — no. Just look at the bit …. Do you need it? Rendering farms in Hollywood? Those in the chip industry interested in unifying the instruction space? On bit systems, you already pay a performance penalty for dealing with pointers that are twice as large.

About the only only practical uses I could see for bits are for filesystems, or for ultra-high-end compute clusters that run thousands or hundreds of thousands of virtuals. Im not arguing for moving to bit memory addressing — we are pretty far away from that becoming useful by any stretch of the imagination. But bit GPRs might be quite useful.

But you point about bit being slower…. Its not slower because of having to work on bit registers. Doubling the size of registers had virtually no detrimental effect on clock speeds. Its slower simply because you in are doubling the amount of data that needs to be moved around the system.

The slowdowns are almost completely isolated to the following areas:. Moving data from the CPU to the caches and main memory and back again takes longer because there is simply more bits to move. And since this is already a bottleneck to performance, the effects are amplified. This is sometimes counteracted by the increase in available registers that came with x, but not often.

Regardless, as caches get bigger and faster the difference will shrink. That is already happening, i7 still has the same problem — but the difference is much less pronounced because the memory subsystem has gotten so much better. And if you happen to actually need to operate on bit integer values routinely, the increase in performance completely trumps all those concerns. There is something sad in both your comments….

Most home computers will have a maximum of GB of memory, which makes the bit architecture a bit of a niche market. Keeping in mind how the switch to bit infrastructure was made nearly a decade ago, one begs to wonder why no further improvements have been made. Although email clients such as Outlook support bit, it is far less widespread than its bit counterpart. From a practical point of view, bit architecture is the pinnacle of what mainstream consumers would ever use.

Increasing to bit, specifically on the operating system level, makes no sense whatsoever at this time. Desktop applications would not necessarily benefit from bit support, nor would server applications. This does not mean there is no need for bit operating systems, though, but the market is too small to start developing these solutions.



0コメント

  • 1000 / 1000