From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: which -march flag to pick for Intel Core 2 Duo in make.conf?
Date: Thu, 24 May 2007 17:30:18 +0200 [thread overview]
Message-ID: <1310969.6LInUspViS@kn.gn.rtr.message-center.info> (raw)
In-Reply-To: d9a0a6da0705240655p741ed606n8a7b3fc3fd7ce972@mail.gmail.com
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?
In the kernel: Yes. At least in 2.6.21.
> And is there explicit support in the latest gentoo kernel for Core 2
> Duo, or does it go under Pentium 4 family?
I'd say, it goes under Core2 -> MCORE2.
Alexander Skwar
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2007-05-24 15:36 UTC|newest]
Thread overview: 9+ 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
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 ` Alexander Skwar [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=1310969.6LInUspViS@kn.gn.rtr.message-center.info \
--to=listen@alexander.skwar.name \
--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