From: "Oliver Kellogg" <oliver.kellogg@t-online.de>
To: gcc@gcc.gnu.org
Subject: Re: [gnat] reuse of ASTs already constructed
Date: Sat, 23 Jun 2012 18:22:00 -0000 [thread overview]
Message-ID: <1SiUyf-1gAVge0@fwd07.aul.t-online.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
Hello,
The patch attached at http://gcc.gnu.org/ml/gcc/2012-06/msg00261.html
was just barely enough to get gnat1 compiled but failed on compiling the
rts files. Please replace it by the patch here. (This one is against
gcc/trunk r162542 of 2010-07-26 but I'm moving forward these days.)
One occasional ALI difference wrt single compile mode is the unit
number appearing in 'X' lines, for example:
--- single/blanks_to_underscores.ali 2012-06-23 18:15:09
+++ multi/blanks_to_underscores.ali 2012-06-23 19:07:39
@@ -7,20 +7,17 @@
.....
-X 3 blanks_to_underscores.adb
+X 1 blanks_to_underscores.adb
In multi source compilations, main units may get assigned different
unit numbers than in single source compilations; this is due to the
reuse of entries in the Lib.Units table.
Is that tolerable?
Thanks,
Oliver
On 2012-06-17 17:12, Oliver Kellogg wrote:
>
> Continuing on from http://gcc.gnu.org/ml/gcc/2012-04/msg00654.html,
> [...]
> Here is my current patch (against trunk r158428), plus a test case
> that demonstrates the fix for the problem described, and also shows
> remaining problems with ALI generation in the multi source compile
> mode.
>
[-- Attachment #2: Type: application/x-gzip, Size: 38052 bytes --]
next reply other threads:[~2012-06-23 18:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 18:22 Oliver Kellogg [this message]
2012-06-23 22:23 ` Arnaud Charlet
-- strict thread matches above, loose matches on Subject: below --
2012-07-07 20:33 Oliver Kellogg
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
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=1SiUyf-1gAVge0@fwd07.aul.t-online.de \
--to=oliver.kellogg@t-online.de \
--cc=gcc@gcc.gnu.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).