public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Shields" <laebshade@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: Thu, 24 May 2007 10:17:27 -0400	[thread overview]
Message-ID: <642958cc0705240717s360e212er3f54e8636e5a06f1@mail.gmail.com> (raw)
In-Reply-To: <d9a0a6da0705240655p741ed606n8a7b3fc3fd7ce972@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 735 bytes --]

On 5/24/07, Denis <denis.che@gmail.com> wrote:
>
> Are these any options in the kernel and in the gcc to optimize for
> Intel's Core 2 Duo chips?  When I set up my gentoo box for the Pentium
> Processor Extreme Edition (dual core prescott), I just used
> -march=prescott in make.conf
>
> Which -march flag would be the most relevant gcc optimization for
> Intel Core 2 Duo?
>
> And is there explicit support in the latest gentoo kernel for Core 2
> Duo, or does it go under Pentium 4 family?
>
> Thanks
> --
> gentoo-user@gentoo.org mailing list
>
>
A gentoo forum thread[1] states to use -march=nocona for Core 2 Duo, and
-march=prescott for Core  Solo/Duo.

[1] http://forums.gentoo.org/viewtopic-p-3602555.html


-- 
- Mark Shields

[-- Attachment #2: Type: text/html, Size: 1183 bytes --]

  parent reply	other threads:[~2007-05-24 14:26 UTC|newest]

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

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=642958cc0705240717s360e212er3f54e8636e5a06f1@mail.gmail.com \
    --to=laebshade@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