public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@upchuck.cygnus.com>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: egcs@egcs.cygnus.com
Subject: Re: Target CPU default selection on alpha
Date: Fri, 18 Dec 1998 19:59:00 -0000	[thread overview]
Message-ID: <10736.914039885@upchuck> (raw)
In-Reply-To: <13946.51325.27183.182995@xayide.TechFak.Uni-Bielefeld.DE>

  In message < 13946.51325.27183.182995@xayide.TechFak.Uni-Bielefeld.DE >you writ
e:
  > Currently gcc/configure.in sets TARGET_CPU_DEFAULT for alpha* targets based
  > on the cpu type of the machine used to configure and build gcc, as
  > determined by config.guess (alpha, alphaev5, alphaev56, alphapca56,
  > alphaev6).  While this is convenient for a single machine, I suppose it may
  > cause problems when the resulting gcc is run on a machine with a different
  > cpu type: e.g. configured for a 21164/ev5, but run on a 21064/ev4.
  > 
  > I'm not sure if this really causes problems on various alpha cpus
  > (cf. SPARC: using hardware multiplication on SPARC V7 machines causes
  > kernel emulation of the relevant instructions), but its more in line with
  > the treatment of other processors to leave this choice to the user (via
  > --with-cpu=).
There's two choices.

1. Generate appropriate code for whatever system you're building on.

2. Generate code for the least common denominator.


Sounds like gcc defaults to #1 for Sparcs, which is fine.  If you want to
generate "common" mode binaries, then you need to configure for the target
which is the least common denominator for your systems.

jeff

  reply	other threads:[~1998-12-18 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-18 13:26 Rainer Orth
1998-12-18 19:59 ` Jeffrey A Law [this message]
1998-12-18 20:31 ` Richard Henderson
1998-12-21  6:05   ` Jeffrey A Law
1998-12-21  8:31     ` David Edelsohn
1998-12-22 13:02       ` Jeffrey A Law
1998-12-21 11:23     ` Rainer Orth
1998-12-22 12:05       ` Jeffrey A Law

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=10736.914039885@upchuck \
    --to=law@upchuck.cygnus.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=ro@TechFak.Uni-Bielefeld.DE \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).