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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,546c9d71cfb0c1ee X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-03-19 01:28:43 PST Path: archiver1.google.com!postnews2.google.com!not-for-mail From: rolf.ebert_nospam_@gmx.net (Rolf Ebert) Newsgroups: comp.lang.ada Subject: Re: [Announcement] New Project: ASIS for GNAT Date: 19 Mar 2004 01:28:43 -0800 Organization: http://groups.google.com Message-ID: <46b8b50a.0403190128.7779d8ee@posting.google.com> References: <1252369.os30E2mMWi@linux1.krischik.com> <87ish8iit1.fsf@insalien.org> <4441304.6rRzW27CSL@linux1.krischik.com> <877jxns0e2.fsf@insalien.org> <1413383.96bL1pG4j9@linux1.krischik.com> <871xnvrqvl.fsf@insalien.org> <1420314.lQdMtk62IO@linux1.krischik.com> <87ekrsdg0r.fsf@insalien.org> <1728933.b9v3IVdcgI@linux1.krischik.com> <46b8b50a.0403180008.2e0f0ce1@posting.google.com> NNTP-Posting-Host: 194.97.67.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1079688523 7408 127.0.0.1 (19 Mar 2004 09:28:43 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 19 Mar 2004 09:28:43 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:6436 Date: 2004-03-19T01:28:43-08:00 List-Id: Georg Bauhaus wrote in message news:... > Rolf Ebert wrote: > : I regularily build gcc from the 3.3 and 3.4 branches on Linux and > : Windows (about once per week) and don't have major problems. (see my > : other posting about ACATS results). > > Interesting. Do you have any experience of whether or not --enable-checking > turns out to be relevant? > No, I have no experience with --enable-checking. I had to look up the doc: << --enable-checking --enable-checking=list When you specify this option, the compiler is built to perform checking of tree node types when referencing fields of that node, and some other internal consistency checks. This does not change the generated code, but adds error checking within the compiler. This will slow down the compiler and may only work properly if you are building the compiler with GCC. This is on by default when building from CVS or snapshots, but off for releases. [...] >> I build gcc from CVS sources, therefor the tested gcc always had checking enabled. I don't see how that has any influence on the ACATS results, though, as it does not change the generated code.