From: Jim Wilson <wilson@cygnus.com>
To: Greg Galloway <gregg@eoeml.gtri.gatech.edu>
Cc: joel@OARcorp.com, law@cygnus.com, egcs@cygnus.com
Subject: Re: EGCS-970929 and GNAT-3.10p?
Date: Thu, 09 Oct 1997 16:12:00 -0000 [thread overview]
Message-ID: <199710092311.QAA26595@cygnus.com> (raw)
In-Reply-To: <199710091528.LAA07015@nospokes.gtri.gatech.edu>
The first show stopper with egcs+gnat is the routine get_inner_reference()
which is defined in gcc/tree.h as taking 8 arguments. It is called from
gcc/ada/a-trans.c with only 7 arguments.
This is a change made to the front-end/back-end interface since the gcc 2.7.2
release which has not been merged into the gnat releases yet.
To workaround it, add a line
int alignment;
and then add to the end of the get_inner_reference call
, &alignment
The gnat-3.11 sources incidentally already (or will) have this change.
Jim
next prev parent reply other threads:[~1997-10-09 16:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-09 9:26 Greg Galloway
1997-10-09 16:12 ` Jim Wilson [this message]
1997-10-15 20:16 ` Jeffrey A Law
1997-10-16 12:50 ` Jim Wilson
-- strict thread matches above, loose matches on Subject: below --
1997-10-16 12:50 Greg Galloway
1997-10-16 12:53 ` Jeffrey A Law
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 ` Jeffrey A Law
1997-10-16 15:19 ` Joel Sherrill
1997-10-16 15:19 ` Joel Sherrill
1997-10-16 15:19 ` Jeffrey A Law
1997-10-16 21:51 ` Richard Henderson
1997-10-17 5:26 ` 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
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=199710092311.QAA26595@cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gregg@eoeml.gtri.gatech.edu \
--cc=joel@OARcorp.com \
--cc=law@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).