From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 64bit vs 32bit
Date: Wed, 21 Jun 2006 14:28:44 +0200 [thread overview]
Message-ID: <200606211428.44586.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <e1a7ee0c0606202226p716cc284qcc4c91f87d86a2e4@mail.gmail.com>
On Wednesday 21 June 2006 07:26, Mike Huber wrote:
> My understanding is that the major advantage of the 64-bit processors
> is for memory address space (>4Gigs of virtual memory space without
> PAE, technically 48 bits of address space, which is something like
> 128Terrabytes of addressable memory).
>
> There must be some advantage associated with being able to hold two
> long ints in one register (or some such relationship there). Anyone
> know detailed explanations for situations where 64-bit is more/less
> beneficial and why?
>
large numbers?
but the 64bit amd extension is really, really helpfull, when you need
registers. The additional registers are a huge advantage and can give you a
nice boost.
Can, not have too - it depends on the task and how the software was compiled.
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-06-21 12:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 19:15 [gentoo-user] 64bit vs 32bit Catalin Trifu
2006-06-16 19:22 ` Justin R Findlay
2006-06-16 19:22 ` Lord Sauron
2006-06-16 21:09 ` Hemmann, Volker Armin
2006-06-19 12:02 ` Pete Pardoe
2006-06-19 12:23 ` Hemmann, Volker Armin
2006-06-19 12:35 ` Gian Domeni Calgeer
2006-06-19 13:54 ` Hemmann, Volker Armin
2006-06-19 14:24 ` Gian Domeni Calgeer
2006-06-19 14:56 ` Neil Bothwick
2006-06-19 18:26 ` kashani
2006-06-19 21:43 ` Hemmann, Volker Armin
2006-06-21 5:26 ` Mike Huber
2006-06-21 12:28 ` Hemmann, Volker Armin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606211428.44586.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox