From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] x86 processor options for opteron 165
Date: Sat, 11 Nov 2006 07:18:48 -0600 [thread overview]
Message-ID: <200611110718.53438.bss03@volumehost.net> (raw)
In-Reply-To: <4555CB4F.20008@pro.onet.pl>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Saturday 11 November 2006 07:08, Piotr Pruszczak
<p.pruszczak@pro.onet.pl> wrote about '[gentoo-amd64] x86 processor
options for opteron 165':
> CFLAGS="-march= ????? -O2 -pipe"
>
> WHAT should I put into ?????
>
> my cpu is Opteron 165 (dual core)
From what I understand, -march=opteron is supported even when building
32-bit code.
--
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-11 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 13:08 [gentoo-amd64] x86 processor options for opteron 165 Piotr Pruszczak
2006-11-11 13:18 ` Boyd Stephen Smith Jr. [this message]
2006-11-11 13:18 ` Simon Stelling
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=200611110718.53438.bss03@volumehost.net \
--to=bss03@volumehost.net \
--cc=gentoo-amd64@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