From: Geert Bosch <bosch@adacore.com>
To: okellogg@users.sourceforge.net
Cc: gcc@gcc.gnu.org
Subject: Re: [gnat] reuse of ASTs already constructed
Date: Mon, 20 Apr 2009 18:40:00 -0000 [thread overview]
Message-ID: <D54EE02C-F57C-4D27-8A65-0C23BDD993D7@adacore.com> (raw)
In-Reply-To: <1239557374.7565.37.camel@tidbit.site>
On Apr 12, 2009, at 13:29, Oliver Kellogg wrote:
> On Tue, 4 Mar 2003, Geert Bosch <bosch at gnat dot com> wrote:
>> [...]
>> Best would be to first post a design overview,
>> before doing a lot of work in order to prevent spending time
>> on implementing something that may turn out to have fundamental
>> problems.
>
> I've done a little experimenting to get a feel for this.
>
> I've looked at the work done toward the GCC compile server but
> decided that I want to concentrate on GNAT trees (whereas the
> compile server targets the GNU trees.)
>
> Also I am aiming somewhat lower - not making a separate compile
> server process but rather extending gnat1 to handle multiple
> files in a single invocation.
While this may be an interesting idea, there are some fundamental
assumptions
in the compiler that each compilation indeed processes a single
compilation unit,
resulting in a single object and .ali file. It would be best to first
contemplate
what output a single invocation of the compiler, with multiple
compilation units
as arguments, should produce.
How would you decide if a unit needs recompilation if there was no 1:1
correspondence between compilation units and object/.ali files?
Note that unlike many other languages, Ada requires checks to avoid
including out-of-date compilation results in a program.
-Geert
next prev parent reply other threads:[~2009-04-20 17:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-07-07 20:33 Oliver Kellogg
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
[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
2009-09-27 22:48 ` 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=D54EE02C-F57C-4D27-8A65-0C23BDD993D7@adacore.com \
--to=bosch@adacore.com \
--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).