From: Jeffrey A Law <law@cygnus.com>
To: Joel Sherrill <joel@OARcorp.com>
Cc: Greg Galloway <gregg@eoeml.gtri.gatech.edu>, egcs@cygnus.com
Subject: Re: EGCS-970929 and GNAT-3.10p?
Date: Thu, 16 Oct 1997 15:19:00 -0000 [thread overview]
Message-ID: <9741.877017103@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.BSF.3.96.971016075832.13079A-100000@vespucci.advicom.net>
In message < Pine.BSF.3.96.971016075832.13079A-100000@vespucci.advicom.net >you write:
> 3.10p and the early August testgcc snapshot I was working with. The
> substitution in Makefile.in as follows:
>
> target=
> target_alias=
>
> Gets botched for target alias.
Hmmm, my gcc/ada/Makefile doesn't have a reference to target_alias:
% grep target_alias Makefile
% grep target= Makefile
target=hppa1.1-hp-hpux10.20
> Both lines end up with target= on the LHS.
> I am not an autoconf expert but it looks like the substitution in the
> language subdirectories is done differently form the main gcc/Makefile.in.
Quite possible -- that stuff has changed a lot recently.
> FYI the vanilla gnat source does not have any references to target_alias,
> program_prefix, or program_transform_name. That was part of ewhat I was
> working on.
Maybe that's why I don't have target_alias in the generated Makefile :-)
Yes, the lack of prefix & transform name will be an issue we'll
have to settle. Part of the generic "fix Ada for cross platforms"
problem.
> > I started poking at gnat-3.10p with egcs a short while ago -- I got
> > gnat1 and gnattools built on the PA. It then died building the
> > library due to a buglet in the gcc-2.7.2 PA binaries provided by
> > the GNAT folks.
>
> I have noticed people in the past griping about the PA.
It should be noted that once I got the first egcs based gnat binary running
it would successfully bootstrap with -O2 or no optimization -- no released
version of gnat can do that as far as I know! (some ada files have to be built
with optimization and others without)
Many of the PA gnat problems can be traced back to Kenner refusing to
fix some C code in the Ada front end which has undefined ANSI behavior.
> It probably looks that way since you probably have no idea how much work
> it is doing. :) It is not really that slow as far as Ada compilers go.
:-) :-) It certainly seems slow to me :-)
jeff
next prev parent reply other threads:[~1997-10-16 15:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-08 14:14 Greg Galloway
1997-10-08 21:19 ` Jeffrey A Law
1997-10-09 9:26 ` Joel Sherrill
1997-10-09 16:31 ` Jim Wilson
1997-10-15 21:43 ` Jeffrey A Law
1997-10-16 2:35 ` Klaus Kaempf
1997-10-16 8:31 ` Jeffrey A Law
1997-10-16 12:53 ` Jim Wilson
1997-10-16 15:19 ` Joel Sherrill
1997-10-16 15:19 ` Jeffrey A Law
1997-10-16 15:19 ` Joel Sherrill
1997-10-16 15:19 ` Jeffrey A Law [this message]
1997-10-16 21:51 ` Richard Henderson
1997-10-16 23:09 ` egcs-971016 Oleg Krivosheev
1997-10-17 14:36 ` egcs-971016 Jeffrey A Law
1997-10-17 5:26 ` EGCS-970929 and GNAT-3.10p? Joel Sherrill
1997-10-17 15:05 ` Toon Moene
1997-10-18 8:45 ` Joel Sherrill
1997-10-23 13:54 ` Toon Moene
1997-10-23 12:49 ` Joel Sherrill
1997-10-09 16:12 ` Jim Wilson
1997-10-09 9:26 Greg Galloway
1997-10-09 16:12 ` Jim Wilson
1997-10-15 20:16 ` Jeffrey A Law
1997-10-16 12:50 ` Jim Wilson
1997-10-16 12:50 Greg Galloway
1997-10-16 12:53 ` 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=9741.877017103@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gregg@eoeml.gtri.gatech.edu \
--cc=joel@OARcorp.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).