From: oliver.kellogg@t-online.de (Oliver Kellogg)
To: gcc@gcc.gnu.org
Subject: Re: [gnat] reuse of ASTs already constructed
Date: Wed, 26 Aug 2009 18:39:00 -0000 [thread overview]
Message-ID: <1251308729.4486.25.camel@tidbit.site> (raw)
In-Reply-To: <1246487007.4507.76.camel@tidbit.site>
I've been making progress on the Ada side, the basic usage pattern for
gnat1 and gnatmake is working.
There are two problems right now:
1) Mixing of Ada.Text_IO and Text_IO as described at
http://gcc.gnu.org/ml/gcc-help/2009-08/msg00113.html
2) The 'X' lines in the ALI files are not what they should be.
This is due to the fact that Lib.Xref.Generate_(Definition|Reference) is
called during semantic analysis. However, when I discover that a
tree was already built for a main unit by a previous compilation,
Sem is not redone for that tree. Depending on whether
Lib.Xref.Initialize is called per-job or per-file, this leads to either
too much or too little cross ref info.
Ideas?
Thanks,
Oliver
On Thu, 2009-07-02 at 00:23 +0200, Oliver Kellogg wrote:
> I am approaching the point where the basic multi-source mechanism
> in the gnat1/gnatmake Ada code is working but I am getting
> lots of crashes in the gigi/gnat_to_gnu triggered core gcc code.
> I will have to learn much more about the GCC internals than
> I know right now so progress will inevitably be slow.
>
> For your information I am appending the current patch that
> I am using, as well as a log of a valgrind session that shows
> some of the current problems.
>
> On Wed, 2009-04-22 at 18:22 -0400, Robert Dewar wrote:
> > Oliver Kellogg wrote:
> > > [...]
> > > One more thing, procedure Initialize crashes with a libc report of
> > > double free() when invoked more than once. (Found this while
> > > working on the gnat1 multi-source compile feature, see
> > > http://gcc.gnu.org/ml/gcc/2009-04/msg00380.html)
> > > FYI I'm attaching the patch that works for me.
> >
> > gnat1 does not have the capability of compiling more than one
> > source file without being loaded, yes there is some preparation
> > for this, but it would require major work to get this working,
> > there are many known problems.
>
> For interest, what are the known problems?
>
> Thanks,
>
> Oliver
>
next parent reply other threads:[~2009-08-26 17:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1240349826.4554.76.camel@tidbit.site>
[not found] ` <49EE4D58.8020404@adacore.com>
[not found] ` <1240437226.4554.101.camel@tidbit.site>
[not found] ` <49EF9892.1010703@adacore.com>
[not found] ` <1246487007.4507.76.camel@tidbit.site>
2009-08-26 18:39 ` Oliver Kellogg [this message]
2009-09-27 22:48 ` Oliver Kellogg
2012-07-07 20:33 Oliver Kellogg
-- strict thread matches above, loose matches on Subject: below --
2012-06-23 18:22 Oliver Kellogg
2012-06-23 22:23 ` Arnaud Charlet
2012-06-17 15:12 Oliver Kellogg
2012-04-15 19:22 oliver.kellogg
2012-04-06 20:24 oliver.kellogg
2012-04-10 10:20 ` Arnaud Charlet
2009-04-13 16:30 Oliver Kellogg
2009-04-14 14:10 ` Oliver Kellogg
2009-04-19 18:48 ` Oliver Kellogg
2009-04-20 5:14 ` Oliver Kellogg
2009-05-03 21:14 ` Oliver Kellogg
2009-05-03 21:17 ` Robert Dewar
2009-05-03 21:22 ` Oliver Kellogg
2009-05-04 1:14 ` Robert Dewar
2009-05-04 5:31 ` Oliver Kellogg
2009-05-04 12:23 ` Dave Korn
2009-05-09 20:09 ` Oliver Kellogg
2009-05-09 20:42 ` Robert Dewar
2009-06-15 20:38 ` Oliver Kellogg
2009-06-17 4:20 ` Oliver Kellogg
2009-06-28 22:45 ` Oliver Kellogg
2009-05-08 21:13 ` Tom Tromey
2009-04-20 18:40 ` Geert Bosch
2009-04-20 20:34 ` Oliver Kellogg
2009-04-20 21:12 ` Geert Bosch
2009-04-20 21:35 ` Oliver Kellogg
2009-04-27 6:18 ` Oliver Kellogg
2009-04-27 8:29 ` Robert Dewar
2009-04-27 18:36 ` Ian Lance Taylor
2009-04-27 18:47 ` Oliver Kellogg
2009-04-27 19:47 ` Tom Tromey
2009-04-27 22:09 ` Oliver Kellogg
2009-04-27 22:26 ` Tom Tromey
2009-04-27 22:44 ` Oliver Kellogg
2003-03-04 22:03 Robert Dewar
2003-03-04 20:42 Robert Dewar
2003-03-04 21:01 ` Oliver Kellogg
2003-03-04 22:03 ` Geert Bosch
2003-03-04 17:08 Oliver Kellogg
2003-03-04 20:07 ` Geert Bosch
2003-03-04 20:49 ` Oliver Kellogg
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=1251308729.4486.25.camel@tidbit.site \
--to=oliver.kellogg@t-online.de \
--cc=gcc@gcc.gnu.org \
--cc=okellogg@users.sourceforge.net \
/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).