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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,78f52dfc9ef24174,start
X-Google-Attributes: gid103376,public
From: Mats.Weber@elca-matrix.ch (Mats Weber)
Subject: Re: DEC Ada V3.3
Date: 1996/09/03
Message-ID: <Mats.Weber-0309961227080001@mlma27.elca-matrix.ch>#1/1
X-Deja-AN: 178174146
organization: ELCA Matrix SA
newsgroups: comp.lang.ada
Date: 1996-09-03T00:00:00+00:00
List-Id: <comp.lang.ada>


>>We also have problems with DEC Ada V3.3 (unexplained Contraint_Errors,
>>unpredictable behavior, duplicate symbols on link of optimized code,
>>access violations, etc.) and we are seriously considering going back to
>>3.2.
>
>I have not seen this sorts of problems reported with Ada V3.3.
>
>If you have a Digital support contract, please report them, with instructions
>for reproducing them.  We have customers running V3.3, and they appear to
>be relatively happy...  ;-)

The symptoms of our problem are the following:

We have a program approx. 100'000 lines of code that, when compiled with
DEC Ada 3.3, behaves in a strange way, with both /optimize and
/nooptimize:
- raises Constraint_Error in a non reproducible way
- some tasks block for 10 secs to 10 minutes without any apparent reason
- when compiled with /optimize, we get the following message at link time:
  "%W, symbol ADA$ADD_ALL$V multiply defined
        in module ADD_ALL file
        USER2:[PTT_APZV.ADA_OPT.EASYFILE]EZF_US-XX319A799C48DA.OBJ;1"

The above symptoms dissapear when we compile the exact same code with
version 3.2 (But we cannot generate an optimized version with 3.2 because
of an internal compiler error).

It is quite hard to isolate the problem to a few packages because the
problems are not easy to reproduce. We haven't been able to reproduce the
problems on our machine: we need to run the program on our customer's
machine to see the problems happen.

Do you think it is worth for us to submit the problem to DEC ?