public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: waltdnes@waltdnes.org
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: i7-6700, anyone already?
Date: Thu, 10 Dec 2015 13:52:49 -0500	[thread overview]
Message-ID: <20151210185249.GA3908@waltdnes.org> (raw)
In-Reply-To: <56691FDB.70104@xunil.at>

On Thu, Dec 10, 2015 at 07:46:51AM +0100, Stefan G. Weichinger wrote
> Am 10.12.2015 um 05:50 schrieb waltdnes@waltdnes.org:
> 
> > CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables -fno-asynchronous-unwind-tables"
> > 
> >   That's what I use, except for cross-compiling.  For an explanation of
> > the "unwind" flags, see thread...
> > http://comments.gmane.org/gmane.linux.busybox/36695  from the busybox
> > mailing list.  And don't forget CPU_FLAGS_X86.  Emerge and run
> > app-portage/cpuinfo2cpuflags as soon as you can during the install
> > process.  I believe that's right after running "eselect profile".  And
> > then run "emerge system && emerge world".  It's a lot quicker when you
> > don't have very much installed on the machine.
> 
> did not know that tool, thanks.
> Will try on my existing box already.
> 
> Do I have to set that variable then (in make.conf?) ?

  Yes, you should.  While you're at it, you can remove the corresponding
flags from the USE= variable.  I don't know if they're honored by
portage any longer.  I assume you missed the news item back in January.
It's archived and you can read it at...
https://www.gentoo.org/support/news-items/2015-01-28-cpu_flags_x86-introduction.html

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


  parent reply	other threads:[~2015-12-10 18:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 22:13 [gentoo-user] OT: i7-6700, anyone already? Stefan G. Weichinger
2015-12-09 20:39 ` Stefan G. Weichinger
2015-12-09 20:42   ` Alan McKinnon
2015-12-09 21:24     ` Stefan G. Weichinger
2015-12-09 21:49       ` Alan McKinnon
2015-12-09 22:03         ` Stefan G. Weichinger
2015-12-10  4:50           ` waltdnes
2015-12-10  6:46             ` Stefan G. Weichinger
2015-12-10  8:51               ` Frank Steinmetzger
2015-12-10 18:52               ` waltdnes [this message]
2015-12-11  9:33                 ` Stefan G. Weichinger
2015-12-13 10:39                   ` Stefan G. Weichinger
2015-12-13 11:50                     ` Stefan G. Weichinger
2015-12-13 12:05                       ` Stefan G. Weichinger
2015-12-15 14:02                         ` Stefan G. Weichinger
2015-12-30 19:00                           ` Stefan G. Weichinger
2015-12-30 22:16                             ` Stefan G. Weichinger
2016-01-04 22:00                               ` Stefan G. Weichinger
2015-12-09 22:44   ` Mick
2015-12-10  6:48     ` Stefan G. Weichinger

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=20151210185249.GA3908@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --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