From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: willy@debian.org (Matthew Wilcox)
Cc: gcc@gcc.gnu.org, willy@debian.org
Subject: Re: PA specifies invalid T_ADAFLAGS
Date: Thu, 25 Apr 2002 15:04:00 -0000 [thread overview]
Message-ID: <200204252014.g3PKEb5K022548@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20020424201229.E5491@parcelfarce.linux.theplanet.co.uk> from "Matthew Wilcox" at Apr 24, 2002 08:12:29 pm
> I'm not terribly familiar with gcc's configure / build system, so I don't
> know who's at fault here. Should PA be specifying this in X_ADAFLAGS?
> Should Ada not be using T_ADAFLAGS like this?
I believe that this suggestion is correct. We should be specifying
X_ADAFLAGS in a "x-" file, or files. It's the host not the
target that's affected by this issue. The appropriate xmake_file
defines need to be added to config.gcc. I think we only want to do
this for the hpux, bsd and osf configurations (ie., those that use
the SOM linker and hppa64). The pro doesn't use space registers.
Linux puts the same value in all the relevant space registers.
Don't know about the memory models for the other elf ports.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2002-04-25 20:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 12:07 John David Anglin
2002-04-24 12:43 ` Matthew Wilcox
2002-04-25 15:04 ` John David Anglin [this message]
2002-04-26 10:56 ` law
2002-04-26 11:28 ` John David Anglin
2002-04-24 13:27 ` Arnaud Charlet
2002-04-24 13:38 ` John David Anglin
2002-04-24 14:28 ` Arnaud Charlet
2002-04-24 22:47 ` John David Anglin
2002-04-26 9:35 ` law
2002-04-26 9:39 ` John David Anglin
2002-04-26 10:43 ` law
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 16:14 Robert Dewar
[not found] <10204260954.AA16645@vlsi1.ultra.nyu.edu>
2002-04-26 8:11 ` Matthew Wilcox
2002-04-26 4:06 Richard Kenner
2002-04-25 22:55 Matthew Wilcox
2002-04-25 21:14 Robert Dewar
2002-04-25 20:52 Robert Dewar
2002-04-25 21:53 ` John David Anglin
2002-04-25 19:58 Robert Dewar
2002-04-25 20:51 ` John David Anglin
2002-04-25 19:45 Robert Dewar
2002-04-25 19:37 Robert Dewar
2002-04-25 19:55 ` John David Anglin
2002-04-25 5:35 Richard Kenner
2002-04-26 10:54 ` law
2002-04-25 3:37 Richard Kenner
2002-04-24 22:08 Robert Dewar
2002-04-24 21:27 Robert Dewar
2002-04-24 20:37 Robert Dewar
2002-04-24 20:44 ` Matthew Wilcox
2002-04-24 21:44 ` John David Anglin
2002-04-24 20:09 Robert Dewar
2002-04-24 20:06 Robert Dewar
2002-04-24 20:26 ` Matthew Wilcox
2002-04-24 21:39 ` John David Anglin
2002-04-24 19:59 Richard Kenner
2002-04-24 22:07 ` John David Anglin
2002-04-25 0:18 ` Arnaud Charlet
2002-04-25 0:49 ` Richard Henderson
2002-04-26 10:51 ` law
2002-04-25 2:47 ` Olivier Hainque
2002-04-25 2:58 ` Michael Matz
2002-04-25 9:25 ` John David Anglin
2002-04-24 10:27 Matthew Wilcox
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=200204252014.g3PKEb5K022548@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gcc@gcc.gnu.org \
--cc=willy@debian.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).