From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Missing CPU options in make menuconfig
Date: Wed, 20 Jul 2016 19:54:25 +0100 [thread overview]
Message-ID: <20160720195425.2291d4f9@digimed.co.uk> (raw)
In-Reply-To: <0a215487-ad19-9a8f-54a4-44b2decf93c7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Wed, 20 Jul 2016 14:33:04 -0400, Fernando Rodriguez wrote:
> I don't use gentoo sources but I remember reading about gentoo patches
> for processor specific optimizations and being tempted to try them. Is
> it possible that is what you're refering to?
>
> The vanilla sources only shows 5 choices for me on amd64:
> (X) Opteron/Athlon64/Hammer/K8
> ( ) Intel P4 / older Netburst based Xeon
> ( ) Core 2/newer Xeon
> ( ) Intel Atom
> ( ) Generic-x86-64
>
> And it shows a different set of options when I run it on an x86 machine.
That's what I get here, but help lists all the ones I get in
gentoo-sources, apart from MNATIVE, which indicates to me that those
options should be available, once I work out how to switch them on.
--
Neil Bothwick
Processor: (n.) a device for converting sense to nonsense at the speed
of electricity, or (rarely) the reverse.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-07-20 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 17:50 [gentoo-user] Missing CPU options in make menuconfig Neil Bothwick
2016-07-20 18:03 ` Alexander Kapshuk
2016-07-20 18:29 ` [gentoo-user] " Holger Hoffstätte
2016-07-21 7:20 ` Neil Bothwick
2016-07-21 12:48 ` Andrew Savchenko
2016-07-20 18:33 ` [gentoo-user] " Fernando Rodriguez
2016-07-20 18:54 ` Neil Bothwick [this message]
2016-07-20 23:38 ` Fernando Rodriguez
2016-07-21 1:07 ` Fernando Rodriguez
2016-07-21 2:56 ` Adam Carter
2016-07-21 7:18 ` Neil Bothwick
2016-07-21 7:17 ` Neil Bothwick
2016-07-21 10:56 ` Fernando Rodriguez
2016-07-21 10:59 ` Fernando Rodriguez
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=20160720195425.2291d4f9@digimed.co.uk \
--to=neil@digimed.co.uk \
--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