public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas Claesson" <andreas.claesson@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf?
Date: Fri, 25 May 2007 19:03:37 +0200	[thread overview]
Message-ID: <72bdee2f0705251003g5075c767pff4252bc9ed28638@mail.gmail.com> (raw)
In-Reply-To: <AA0639A1EB70AE409130258CE7BDC31806646B17@messenger.cv63.navy.mil>

On 5/25/07, burlingk@cv63.navy.mil <burlingk@cv63.navy.mil> wrote:
>
> > -----Original Message-----
> > From: Randy Barlow [mailto:randy@electronsweatshop.com]
>
> <Snip>
>
> > If you are using a lot of memory in your computations, then
> > the 64-bit environment will be much friendlier to you :)
> > Also, if I understand correctly, you will get higher
> > precision on floating point calculations (someone correct me
> > if I am wrong here!)  I also believe that the 64 bit
> > processors are able to perform more instructions per second
> > on average when executing 64 bit code vs. 32 bit code if I am
> > not mistaken...
>
> I am not sure, but that makes sense.  If nothing else, things executed
> directly usually run more smoothly than those who are run through
> emulation.  64bit code on 64bit processor good...

There is no emulation involved when running 32bit code in either core2
 nor amd64 processors. The difference when running in 32bit mode is
that some instructions are unavailable, you have a smaller number of
registers, and the registers are only 32bit.

More registers speed up most kind of code, 64bit registers speed up
64bit calculations, and the extra instructions are good for array
calculations and similar (more sse instructions for example).

The only bad thing with 64bit code is that the programs get bigger,
which may effect memory performance negatively. But if you have a lot
of memory then you will benefit from not needing any special
addressing modes.

Since you (Denis) are doing a lot of mathematical calculations you
will probably benefit from running in 64bit mode.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-05-25 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-25  9:10 [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf? burlingk
2007-05-25 17:03 ` Andreas Claesson [this message]
2007-05-25 18:26   ` Denis
2007-05-28  3:05     ` Randy Barlow
2007-05-31  1:11     ` Dan Farrell
  -- strict thread matches above, loose matches on Subject: below --
2007-05-24 13:55 Denis
2007-05-24 14:15 ` Ryan Sims
2007-05-24 14:17 ` Mark Shields
2007-05-24 15:13   ` Denis
2007-05-24 15:43     ` Neil Bothwick
2007-05-24 15:55       ` Graham Murray
2007-05-24 16:38       ` Denis
2007-05-25  7:22         ` Randy Barlow

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=72bdee2f0705251003g5075c767pff4252bc9ed28638@mail.gmail.com \
    --to=andreas.claesson@gmail.com \
    --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