From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: drow@mvista.com (Daniel Jacobowitz)
Cc: Richard.Earnshaw@arm.com, gcc-patches@gcc.gnu.org
Subject: Re: RFC: New approach to --with-cpu
Date: Thu, 01 Aug 2002 11:40:00 -0000 [thread overview]
Message-ID: <200208011839.g71Idjtt004954@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20020801152250.GA14239@nevyn.them.org> from "Daniel Jacobowitz" at Aug 1, 2002 11:22:50 am
> On Thu, Aug 01, 2002 at 11:15:10AM -0400, John David Anglin wrote:
> > > + hppa*-*-* | parisc*-*-*)
> > > + if test x$gas = xyes
> > > + then
> > > + target_cpu_default2="MASK_GAS|MASK_JUMP_IN_DELAY"
> > > + fi
> > > + case $machine in
> > > + hppa1* | parisc1*)
> > > + with_cpu=7100LC
> > ^^^^^^^^
> >
> > I believe that this should be "with_schedule". I was also wondering
> > if a comment should be added to indicate that the default scheduling
> > model is "8000".
>
> And you're completely correct on both counts. I've added that to my
> working copy.
I enclose below an update to above code. I have attempted to
bullet proof it so that it handles error conditions gracefully
and only overrides the PA8000 default based on the target
cpu when the user doesn't specify --with-schedule.
I have run through partial builds checking most of the option
permutations and the patch seems to be working well. I like
the ease with which the scheduling model can now be specified.
The only additional wish is for an easy way to print the target
defaults.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
--- config.gcc.orig 2002-08-01 09:36:20.000000000 -0700
+++ config.gcc 2002-08-01 11:19:24.000000000 -0700
@@ -2908,9 +2908,21 @@
then
target_cpu_default2="MASK_GAS|MASK_JUMP_IN_DELAY"
fi
- case $machine in
- hppa1* | parisc1*)
- with_cpu=7100LC
+ case ".$with_schedule" in
+ .700 | .7100 | .7100LC | .7200 | .7300 | .8000)
+ ;;
+ .)
+ case $machine in
+ hppa1* | parisc1*)
+ # Override default PA8000
+ # scheduling model.
+ with_schedule=7100LC
+ ;;
+ esac
+ ;;
+ *)
+ echo "Unknown cpu used with --with-schedule=$with_schedule" 1>&2
+ exit 1
;;
esac
;;
next prev parent reply other threads:[~2002-08-01 18:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 18:54 John David Anglin
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 [this message]
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=200208011839.g71Idjtt004954@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=Richard.Earnshaw@arm.com \
--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).