public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gcc-patches@gcc.gnu.org
Cc: drow@mvista.com
Subject: Re: RFC: New approach to --with-cpu
Date: Tue, 30 Jul 2002 18:54:00 -0000	[thread overview]
Message-ID: <200207310131.g6V1VfNE021308@hiauly1.hia.nrc.ca> (raw)

From a PA standpoint, the main objection that I have to this approach
is that there seems to be a slight loss of flexibility.  You use "with_cpu"
to set the default scheduling model.  However, I was also planning to set
the default arch based on the target machine when a linker bug in handling
PA2.0 code is fixed.  I view these options as independent although the
configure defaults would both be based on the target triplet.  Thus,
it would be necessary to introduce a new configure option to handle
the arch default.  In the future, I can see other default code generation
options being set-table.

I must admit that I don't really like the multilib concept and find
it a rather  idea to build libraries for all scheduling models,
archs, etc.  Thus, I don't find this justification attractive.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

             reply	other threads:[~2002-07-31  1:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 18:54 John David Anglin [this message]
2002-07-30 23:03 ` Daniel Jacobowitz
2002-07-31  7:53   ` John David Anglin
2002-07-31  8:09     ` Daniel Jacobowitz
2002-07-31  8:30       ` Richard Earnshaw
2002-07-31  9:02         ` Daniel Jacobowitz
2002-07-31 10:34           ` John David Anglin
2002-07-31 13:27             ` Daniel Jacobowitz
2002-08-01  3:31               ` Richard Sandiford
2002-08-01  3:57                 ` Richard Earnshaw
2002-08-01  8:15               ` John David Anglin
2002-08-01  8:23                 ` Daniel Jacobowitz
2002-08-01 11:40                   ` John David Anglin
2002-08-01  6:30             ` Richard Earnshaw
2002-08-01  7:41               ` John David Anglin
     [not found] <20020801125224.GA5374@nevyn.them.org>
2002-08-01  6:04 ` Richard Earnshaw
2002-08-01  6:25   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2002-07-30 15:27 Daniel Jacobowitz
2002-07-31  6:35 ` Richard Sandiford
2002-07-31  6:41   ` Daniel Jacobowitz
2002-07-31  6:54     ` Richard Sandiford
2002-07-31  7:28       ` Daniel Jacobowitz
2002-07-31  7:36         ` Richard Sandiford
2002-07-31  7:46           ` Daniel Jacobowitz
2002-07-31  7:50             ` Richard Sandiford
2002-07-31  8:04               ` Daniel Jacobowitz

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=200207310131.g6V1VfNE021308@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=drow@mvista.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).