public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: law@cygnus.com
Cc: Richard Henderson <rth@cygnus.com>, egcs@egcs.cygnus.com
Subject: Re: Target CPU default selection on alpha
Date: Mon, 21 Dec 1998 11:23:00 -0000	[thread overview]
Message-ID: <13950.40985.756783.276976@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <8333.914215139@upchuck>

> The PA (and other) ports have always done it like the alpha too.

From a quick check of current CVS configure.in, the c*-convex-*, several
hppa1.1-*-* and hppa2*-*-*, the i[4-7]86-*-* and alpha*-*-* targets behave
this way.  All others default to the least common denominator.

> There isn't any kind of consistency in this area.  For example the ppc
> defaults to "common" mode.

Than perhaps now it's time to become consistent, or at least document why
some targets have a different default.

> It's not 100% clear that either choice is right.  There's arguments for
> and against defaulting to the least common denominator for code generation.

What are the primary arguments against defaulting to least common
denominator, beyond performance?

I think the decision should be left to the user.  Or at least the user
should be aware of the choice and it's consequences.

	Rainer

  parent reply	other threads:[~1998-12-21 11:23 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
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 [this message]
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=13950.40985.756783.276976@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=egcs@egcs.cygnus.com \
    --cc=law@cygnus.com \
    --cc=rth@cygnus.com \
    /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).