From: Matthias Bethke <matthias@towiski.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Best choice for a dual core
Date: Fri, 28 Jul 2006 23:14:45 +0200 [thread overview]
Message-ID: <20060728211445.GA785@huxley> (raw)
In-Reply-To: <44C8BB28.5080202@mid.message-center.info>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
Hi Alexander,
on Thursday, 2006-07-27 at 15:10:00, you wrote:
> If not, then you won't use those advantages either. Somebody correct
> me, but if you want to WORK with this machine (ie. not fiddle), I'd
> suggest to stay 32bit. Or what advantages would 64bit provide?
Depends a lot on the code[tm]. Some things benefit a lot from a decent
number of registers. OTOH, fiddling with pointers in memory slows things
down as compared to 32bit.
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-28 21:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 12:29 [gentoo-user] Best choice for a dual core Thierry de Coulon
2006-07-27 12:41 ` Alexander Skwar
2006-07-27 13:04 ` Thierry de Coulon
2006-07-27 13:10 ` Alexander Skwar
2006-07-27 13:21 ` Thierry de Coulon
2006-07-28 21:14 ` Matthias Bethke [this message]
2006-07-27 17:40 ` Alan
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=20060728211445.GA785@huxley \
--to=matthias@towiski.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