public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Locate and Fix .text Relocations (TEXTRELs)
Date: Fri, 14 Jul 2006 09:43:25 -0700	[thread overview]
Message-ID: <7573e9640607140943o201dd80ey1d0be80d5d3ce572@mail.gmail.com> (raw)
In-Reply-To: <878xmwtpn7.fsf@newton.gmurray.org.uk>

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



      reply	other threads:[~2006-07-14 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  7:43 [gentoo-user] Locate and Fix .text Relocations (TEXTRELs) Arnau Bria
2006-07-13  9:22 ` Arnau Bria
2006-07-13 18:12 ` Richard Fish
2006-07-14  7:57   ` Arnau Bria
2006-07-14  8:30     ` Richard Fish
2006-07-14  9:18       ` Arnau Bria
2006-07-14 11:03       ` Graham Murray
2006-07-14 16:43         ` Richard Fish [this message]

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=7573e9640607140943o201dd80ey1d0be80d5d3ce572@mail.gmail.com \
    --to=bigfish@asmallpond.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