From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B4D381381F3 for ; Thu, 24 Oct 2013 10:58:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 34C46E09C0; Thu, 24 Oct 2013 10:58:19 +0000 (UTC) Received: from mail-oa0-f52.google.com (mail-oa0-f52.google.com [209.85.219.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 33636E08D9 for ; Thu, 24 Oct 2013 10:58:17 +0000 (UTC) Received: by mail-oa0-f52.google.com with SMTP id n10so2157384oag.25 for ; Thu, 24 Oct 2013 03:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=dta0pmeoBvirIXU9jTUW6PPHDDtszL9U4tUoY3Yf0i0=; b=d9fsCDeRyTD7PjRx9LeM8qevtSh7HDa2KgrORuxhoR+K1sL4PkqAaDLVcB0v36K82z ykH3Z1vpRUtMMLCZPwwNekY4+jSCLfvpzs/VmqLFbY/DHbwT730ZCc9i7QglvkDydSNO 7BsC5UG5GN8+7WBWq8oc+2VA/zIMWa3QUwm99pYqbwHHctVJbak1PXxKXnfoxSuwBwo8 0alz078yaNftVMLIT8yOFU58cbkZK2ku23H4jZdAcadEMFBqIgvMHiw9rJmtJpePbqPH Hilr2qzIxEJ5PqsYHayt8OYTzZ+IZjZC6k/dfkxrYEx+OupBHCnSwyyIjC/yvG9ZJLAR G5CQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.60.65.227 with SMTP id a3mr1651468oet.13.1382612297215; Thu, 24 Oct 2013 03:58:17 -0700 (PDT) Received: by 10.182.50.106 with HTTP; Thu, 24 Oct 2013 03:58:17 -0700 (PDT) In-Reply-To: <5268E324.4030900@gmail.com> References: <5268E324.4030900@gmail.com> Date: Thu, 24 Oct 2013 21:58:17 +1100 Message-ID: Subject: Re: [gentoo-user] Kernel ricing From: Adam Carter To: "gentoo-user@lists.gentoo.org" Content-Type: multipart/alternative; boundary=001a11c25700d6742004e97a8286 X-Archives-Salt: 2c314448-7b6f-4c4e-8540-887ea619b926 X-Archives-Hash: 0462c14a23bbd35238db2305f5c2edc7 --001a11c25700d6742004e97a8286 Content-Type: text/plain; charset=ISO-8859-1 > > I see all you've done is specify -march; what does the build system > build for without that setting? > > Does your question imply that more may happen to the CFLAGs than them just being passed to gcc? I have no idea, so just assumed gcc does whatever it does when no -march is supplied, which i guess is just generic x86-64 stuff. I figured that just -march=amdfam10 was a good start, since it implies MMX, SSE, SSE2, SSE3, SSE4A, 3DNow!, enhanced 3DNow! and ABM, but i may add the rest of my make.conf CFLAGs since I dont have any issues with any other software on this system. Is that fair reasoning? --001a11c25700d6742004e97a8286 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I see all you've done is specify -march; what does the build system
build for without that setting?


Does your question imply= that more may happen to the CFLAGs than them just being passed to gcc? I h= ave no idea, so just assumed gcc does whatever it does when no -march is su= pplied, which i guess is just generic x86-64 stuff.

I fig= ured that just -march=3Damdfam10 was a good start, since it implies MMX, SS= E, SSE2, SSE3, SSE4A, 3DNow!, enhanced 3DNow! and ABM, but i may add the re= st of my make.conf CFLAGs since I dont have any issues with any other softw= are on this system. Is that fair reasoning?
--001a11c25700d6742004e97a8286--