Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #47583
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: 32 bit VS 64 bit modes |
| Date | 2016-05-28 10:07 +0000 |
| Organization | Institut fuer Computersprachen, Technische Universitaet Wien |
| Message-ID | <2016May28.120710@mips.complang.tuwien.ac.at> (permalink) |
| References | <496341e2-6ac8-4bcc-903e-c9e39e3495ae@googlegroups.com> |
Jason Damisch <jasondamisch@yahoo.com> writes:
>I admit not being the most adroit computer programmer or user
>in the world. So, I thought that I'd ask, if people don't mind
>too much, what the various trade-offs and advantages are between
>32 bit and 64 bit modes. For 16 bit VS 32 bit the advantages
>are obvious. But, it seems to me that 32 VS 64 has diminishing
>returns. Maybe 40 bit would be ideal? What reasons could there
>possibly be for having more than 4 GB of RAM?
For having more? Because you can afford it. I recently bought a
cheap CPU, motherboard, cooler, and RAM. I had to decide whether to
buy 4GB for something like EUR20 or 8GB for EUR30 to go with the EUR30
CPU and the EUR 46 mainboard. I decided to buy 8GB. And sizes are
growing over time: Moore's law in action.
For using more? For some applications, you don't need more, for
others, using more helps. E.g. the game Runes of Magic is a 32-bit
program that crashes if the RAM usage goes above about 1.6GB, even on
a machine with 16GB. If it was a 64-bit application, these crashes
probably would not happen. In-Memory databases are a big topic these
days, and they often use more than 4GB. Or, in the Forth world I used
more than 4GB for something quite a while ago (IIRC it was
<https://www.complang.tuwien.ac.at/forth/programs/sbpcp.fs>).
One can also benefit from having larger integers. Also dependent on
the application.
Finally, in the case of AMD64 and Aarch64, the 64-bit architectures
provide additional benefits, in particular, more registers than the
32-bit architecture. That was the main point of my original posting:
Gforth uses the additional registers on Aarch64 for better stack
caching, i.e., faster execution.
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2016: http://www.euroforth.org/ef16/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
32 bit VS 64 bit modes Jason Damisch <jasondamisch@yahoo.com> - 2016-05-27 11:21 -0700
Re: 32 bit VS 64 bit modes Paul Rubin <no.email@nospam.invalid> - 2016-05-27 13:06 -0700
Re: 32 bit VS 64 bit modes Jason Damisch <jasondamisch@yahoo.com> - 2016-05-27 13:22 -0700
Re: 32 bit VS 64 bit modes hughaguilar96@gmail.com - 2016-05-27 13:59 -0700
Re: 32 bit VS 64 bit modes anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-05-28 10:07 +0000
Re: 32 bit VS 64 bit modes Paul Rubin <no.email@nospam.invalid> - 2016-05-28 19:09 -0700
Re: 32 bit VS 64 bit modes Paul Rubin <no.email@nospam.invalid> - 2016-05-28 20:00 -0700
Re: 32 bit VS 64 bit modes Albert van der Horst <albert@cherry.spenarnc.xs4all.nl> - 2016-05-29 17:46 +0000
Re: 32 bit VS 64 bit modes Paul Rubin <no.email@nospam.invalid> - 2016-05-29 11:27 -0700
Re: 32 bit VS 64 bit modes Rod Pemberton <NoHaveNotOne@bcczxcfre.cmm> - 2016-05-28 23:42 -0400
csiph-web