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,f1efe20cb462d89c,start
X-Google-Attributes: gid103376,public
From: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: gnat 3.07 DOS
Date: 1997/01/21
Message-ID: <5c36l5$5u3@top.mitre.org>#1/1
X-Deja-AN: 211438799
organization: The MITRE Corporation, Bedford Mass.
keywords: gnat 3.07 DOS EXE
newsgroups: comp.lang.ada
summary: EXEs are even bigger until stripped
Date: 1997-01-21T00:00:00+00:00
List-Id: <comp.lang.ada>


Preliminary Feedback: the gnat 3.07 DOS: (1) More things work 
than worked under 3.05. (2) Some things work a lot faster.
(3) All EXEs are about twice as big as gnat 3.05 before stripping,
but they strip (using SLIMFAST.BAT) down to about 10K more 
than their 3.05 size, (4) There may be a couple of new problems.
First, we may have to start a new stream_IO thread, because
we seem to be getting extra carriage returns on some stream_io
writes. I am not sure yet, but it seems that when you write to 
a stream_io file or a text_io stream file to the console (no pipe)
it looks about right, but when you write a a text_io stream
to a pipe to a file, it may be writing an extra carriage return.
Also, some applications that worked under 3.05 are getting 
sigseg interrupt 08 DOS hangs. As a result it will take a 
couple of days to test the public domain software we were using.

Things someone could look into: (A) Were the symbols REALLY stripped
from the runtime routines? (B) How can we write streams of bytes
in a way that they work the same way from a pipeline or to
an internally opened filename, preferably in a way that works
unchangingly between DOS and un*x? 

If preliminary testing does not eliminate any problems, they will
be submitted as bug reports.