From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-46395-garchives=archives.gentoo.org@gentoo.org>)
id 1G1RBa-0004Yu-Vx
for garchives@archives.gentoo.org; Fri, 14 Jul 2006 17:10:43 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k6EGwqQp011060;
Fri, 14 Jul 2006 16:58:52 GMT
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168])
by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k6EGhRXT002829
for <gentoo-user@lists.gentoo.org>; Fri, 14 Jul 2006 16:43:28 GMT
Received: by ug-out-1314.google.com with SMTP id h2so856094ugf
for <gentoo-user@lists.gentoo.org>; Fri, 14 Jul 2006 09:43:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
b=OinwWU17uE8iM6FNnlzlBlrcu2Vg7iDZ00xFBSIKKq5PlZxNvUq9/IRos7RqfSr6h1FjKVLywTeI9KpCIqJNLtA11NvNRYLGaMdJ51fuZArxk8HLSsnpOcgyxuILIdc3lnu0lHOsoKV7Iq5EgVSnrnTCJyyJDVAOlhciBP5agFo=
Received: by 10.78.151.15 with SMTP id y15mr1803898hud;
Fri, 14 Jul 2006 09:43:26 -0700 (PDT)
Received: by 10.78.16.7 with HTTP; Fri, 14 Jul 2006 09:43:25 -0700 (PDT)
Message-ID: <7573e9640607140943o201dd80ey1d0be80d5d3ce572@mail.gmail.com>
Date: Fri, 14 Jul 2006 09:43:25 -0700
From: "Richard Fish" <bigfish@asmallpond.org>
Sender: richard.j.fish@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Locate and Fix .text Relocations (TEXTRELs)
In-Reply-To: <878xmwtpn7.fsf@newton.gmurray.org.uk>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060713094303.0d821682@lx-arnau.pic.es>
<7573e9640607131112y44ec99aand717c2b638005bb4@mail.gmail.com>
<20060714095741.7b36081c@lx-arnau.pic.es>
<7573e9640607140130x4bd66f65l2a95078da747df5b@mail.gmail.com>
<878xmwtpn7.fsf@newton.gmurray.org.uk>
X-Google-Sender-Auth: bcdfaacd1bb2593f
X-Archives-Salt: 1710433d-f993-413f-8ab2-625fc9baebb0
X-Archives-Hash: 959acf5c92157d3af1173c61c1741c3b
On 7/14/06, Graham Murray <graham@gmurray.org.uk> wrote:
> "Richard Fish" <bigfish@asmallpond.org> writes:
>
> > Hrm, these are really not sane. -march is telling gcc to build C code
> > that will only run on a p4, and then you have -mtune specifying to run
> > on everything back to a pentium-II. I *think* -march takes precedence
> > here....
>
> Does it? I would have thought that having both -march and -mtune would
> be valid, but normally would be other way round by having, for
> example, '-march=i686 -mtune=pentium4' to build code which will run on
> a pentium-II or later but optimised for running on a P4.
Right, this is the normal case. But in some sense, you could also
consider -march to have precedence here. If it ever needs to make a
choice between generating optimized code for a p4, or code that will
run on a P-II, gcc will choose the P-II compatible code.
But the fact is that I am not sure what -march=pentium4 -mtune=i686
would generate...
-Richard
--
gentoo-user@gentoo.org mailing list