From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c2b3e0a81ca523a4
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2004-04-14 05:33:07 PST
Path: 
 archiver1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!sdn-ap-012tnnashp0038.dialsprint.NET!not-for-mail
From: "Marc A. Criley" <mcNOSPAM@mckae.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada compiler
Date: Wed, 14 Apr 2004 07:32:57 -0500
Message-ID: <c5jb20$2c4k5$1@ID-218515.news.uni-berlin.de>
References: <c0630a89.0404090635.2755fb7@posting.google.com>
 <GyAdc.8$QV3.3@dfw-service2.ext.ray.com>
 <c5eie0$nos0$1@ID-218515.news.uni-berlin.de>
 <c0630a89.0404140123.70e953f1@posting.google.com>
NNTP-Posting-Host: sdn-ap-012tnnashp0038.dialsprint.net (63.189.240.38)
X-Trace: news.uni-berlin.de 1081945986 2495109 I 63.189.240.38 ([218515])
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Xref: archiver1.google.com comp.lang.ada:7087
Date: 2004-04-14T07:32:57-05:00
List-Id: <comp.lang.ada>


"Sergey" <cjkywt@hotmail.com> wrote in message
news:c0630a89.0404140123.70e953f1@posting.google.com...
> "Marc A. Criley" <mcNOSPAM@mckae.com> wrote in message
> > Ditto, this is what I do, never had any problems with it.
> > I compile the exact same code from the 3.15p baseline under gcc 3.2.3
and it
> > compiles and runs fine--I've noticed no differences in execution. (And I
> > admit being a bit surprised about my lack of problems given the reports
of
> > 3.2 problems.) The only compilation difference is 3.2.3 warnings that
the
> > pragma "Unreferenced" is unknown.
>
> Ok, I don't know exactly but the only thing that I can said for
> certain - it isn't that good. I've tried to compile aws-1.4.0 using
> 3.2.3. Compilation finished well, but regression tests have badly
> failed...

Hunh, that's very curious. Have you been able to track it down to specific
lines of code or constructs that aren't executing correctly? I'm curious,
it'd be interesting (to me, anyways :-) to see just what kind of constructs
aren't compiling correctly.

DTraq uses the aforementioned tasking, as well as (gnat) sockets, stream I/O
and attributes, dynamic allocation of objects and tasks, tagged and derived
types, protected objects, child packages, generics--pretty much the whole
gamut of language features, and nothing yet appears to be acting up for me.

Marc