public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Puchmayr <alexander.puchmayr@linznet.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CPU upgrade and LVM questions.
Date: Sat, 08 Dec 2018 18:49:26 +0100	[thread overview]
Message-ID: <1806505.2jTXcQcuRp@zeus> (raw)
In-Reply-To: <492d8bf4-4b8d-f7f6-05d8-2473b6825fab@gmail.com>

Am Donnerstag, 6. Dezember 2018, 10:27:31 CET schrieb Dale:
> Howdy,
> 
> I mentioned in other threads that I'm doing some upgrades to my system. 
> My first question is about a CPU upgrade.  I currently have this for my
> CPU, from cpuinfo:
> 
> AMD Phenom(tm) II X4 955 Processor
> 
> I've bought but not yet installed a FX-8350 CPU.  I have this in my
> make.conf file:
> 
> CFLAGS="-march=native -O2 -pipe"

Compiling the whole system with -march=native might lead to troubles, 
especially when doing a CPU change. This option means that gcc is determining 
the type of CPU automatically and adjusts the instruction set used to exactly 
this CPU. Although, in your case, it is highly likely that your new CPU 
understands all commands from the old, but I wouldn't bet on it. Its possible 
that your existing software encounters problems like "illegal instruction" or 
the like. Very bad if your compiler crashes after CPU replacement, then you 
cannot emerge anything. I highly recommend using CFLAGS="-O2 -pipe" and 
nothing more, the performance difference is, if measurable at all, negligible. 

> USE_CPU="fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc
> extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic
> cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
> nodeid_msr hw_pstate npt lbrv svm_lock nrip_save"
> 
As someone else in this thread already mentioned, USE_CPU is not used. What 
you're looking for is CPU_FLAGS_X86=..., which defines what cpu-specific options 
will be enabled for packages supporting it and where it makes sense. See 
package cpuid2cpuflags for details.

Regards
	Alex





  parent reply	other threads:[~2018-12-08 17:49 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  9:27 [gentoo-user] CPU upgrade and LVM questions Dale
2018-12-06 10:03 ` Neil Bothwick
2018-12-06 15:17   ` Dale
2018-12-06 16:51   ` J. Roeleveld
2018-12-06 18:36 ` Corbin Bird
2018-12-06 20:58   ` Dale
2018-12-06 21:24     ` Jack
2018-12-06 21:55       ` Dale
2018-12-07  1:06     ` Corbin Bird
2018-12-07  1:17       ` Dale
2018-12-07  5:10         ` Dale
2018-12-07  6:22           ` [gentoo-user] " Nikos Chantziaras
2018-12-07  7:30             ` Dale
2018-12-07 10:49               ` Alec Ten Harmsel
2018-12-07 23:47               ` Nikos Chantziaras
2018-12-07 23:59                 ` Dale
2018-12-09 18:23                 ` Taiidan
2018-12-09 18:57                   ` J. Roeleveld
2018-12-09 22:41                     ` Dale
2018-12-10 21:33                     ` Taiidan
2018-12-10 22:14                       ` Neil Bothwick
2018-12-10 22:54                         ` Dale
2018-12-11  2:00                           ` Taiidan
2018-12-11  8:49                             ` Neil Bothwick
2018-12-11  9:23                               ` Mick
2018-12-11 10:48                               ` Dale
2018-12-11 15:14                                 ` J. Roeleveld
2018-12-11 22:46                               ` Adam Carter
2018-12-11 23:56                                 ` Dale
2018-12-12  2:15                                   ` Adam Carter
2018-12-11 10:20                             ` Alan Mackenzie
2018-12-11 15:03                             ` J. Roeleveld
2018-12-07  8:47         ` [gentoo-user] " Neil Bothwick
2018-12-07  8:58           ` Dale
2018-12-06 21:02 ` [gentoo-user] " Nikos Chantziaras
2018-12-06 21:45   ` Dale
2018-12-06 22:22     ` Nikos Chantziaras
2018-12-06 23:23       ` Dale
2018-12-06 23:40         ` Nikos Chantziaras
2018-12-07  0:19           ` Dale
2018-12-07 10:01             ` Peter Humphrey
2018-12-07 12:41               ` Dale
2018-12-07 16:51                 ` Peter Humphrey
2018-12-08  1:01                   ` Dale
2018-12-08  2:51                     ` Nikos Chantziaras
2018-12-08  4:39                       ` Dale
2018-12-08  5:33                       ` David Haller
2018-12-08  5:45                         ` Dale
2018-12-08  6:00                         ` Nikos Chantziaras
2018-12-08  6:28                           ` David Haller
2018-12-08  4:23                 ` David Haller
2018-12-08  5:35                   ` Dale
2018-12-08  6:06                     ` David Haller
2018-12-08  5:38                   ` David Haller
2018-12-08  9:40                     ` Peter Humphrey
2018-12-08  9:50                       ` Peter Humphrey
2018-12-06 21:03 ` [gentoo-user] " Grant Taylor
2018-12-09 22:45   ` Dale
2018-12-10  1:35     ` Grant Taylor
2018-12-10  2:38       ` Dale
2018-12-10  3:37         ` Grant Taylor
2018-12-10  9:27         ` Neil Bothwick
2018-12-10 16:00           ` Dale
2018-12-08 17:49 ` Alexander Puchmayr [this message]
2018-12-08 18:23   ` Dale
2018-12-08 19:09     ` J. Roeleveld
2018-12-08 20:48       ` Dale
2018-12-11 10:41 ` Dale
2018-12-22 23:58 ` Dale

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=1806505.2jTXcQcuRp@zeus \
    --to=alexander.puchmayr@linznet.at \
    --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