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-Thread: 103376,5e062f5bcdb88fd8 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Alex R. Mosteo" Newsgroups: comp.lang.ada Subject: Re: gnat 3.15p/Windows and tasking bug Date: Mon, 24 Jul 2006 16:12:54 +0200 Message-ID: <4ik2m3F45ofgU1@individual.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: individual.net Rkej07yyShGBlDbVYYImYAbU8UPgvkAuTZxOavUsDzwqvRxeA= User-Agent: KNode/0.10.2 Xref: g2news2.google.com comp.lang.ada:5897 Date: 2006-07-24T16:12:54+02:00 List-Id: michael bode wrote: > I (and Google) remember a discussion about a bug in gnat 3.15p for > Windows regarding tasking and delay statements that delay much longer > than they should sometimes. What I don't remember and also did not > find through Google was a precise description and if there was a > workaround or some success using gcc-gnat 3.4.x (3.4.5 is the current > MinGW version I think). > > To be precise I found references to TWO such bugs one of them was > limited to rather old mainboards or chipsets. I'm searching for > information on the other bug. I keep a copy of my old patch for gnat 3.15p/win. You could try comparing these files to the original ones to find the diffs, and also compare them to the mingw ones. I think that 3.15p was still 2.x based, so maybe they're too different. Anyhow, the files are here: https://svn.mosteo.com/public/adagio/gnatpatch/ I strongly suspect the only one with modifications is s-tasren.adb, the others are simply there because they had to be recompiled because of dependencies. However this is just a fuzzy recall. What I can say is that when recompiling these files and linking them with my program, the bug went away. I received two different patches, but can not remember their origins. I kept the most recent one, the older one caused some other bug. To compile, gnatmake -u -a *.ad? and then include the objects for linking. The other way is to recompile the entire gnat runtime with the patched sources. I preferred the first way so I was sure that any stock unmodified 3.15p installation would serve. Hope this helps.