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-Thread: a07f3367d7,a4db0fc323f0b09e
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news1.google.com!news.glorb.com!feeder.erje.net!feeder.eternal-september.org!eternal-september.org!not-for-mail
From: Reto Buerki <reet@codelabs.ch>
Newsgroups: comp.lang.ada
Subject: Re: Barrier re-evaluation issue with GNAT 4.3.2
Date: Mon, 28 Sep 2009 12:18:08 +0200
Organization: A noiseless patient Spider
Message-ID: <h9q2gk$k3a$1@news.eternal-september.org>
References: <h9g8mf$v4f$1@news.eternal-september.org>
 <qheeig65rowe.1x18w150lpl1q.dlg@40tude.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: news.eternal-september.org
 U2FsdGVkX1/N+LQWO8zYtUleSWtOeqMPiAk54bGkBI9uRQPAhcMzuUidugmnc8z4A5Dm24T5YkVWAPwzleiOWzdI8hOq5qSOHPtEXfaJ+/+8hiTDvPLlq/j5sGuzgtsdzQtRSQuTgsgUYlG36z5umA==
X-Complaints-To: abuse@eternal-september.org
NNTP-Posting-Date: Mon, 28 Sep 2009 10:17:57 +0000 (UTC)
In-Reply-To: <qheeig65rowe.1x18w150lpl1q.dlg@40tude.net>
X-Auth-Sender: U2FsdGVkX18+nOonbTMfNs8dCiKI+JqhedljZwgX67I=
Cancel-Lock: sha1:n6q6J66TeTVSjbadQj486ztgNVs=
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706)
Xref: g2news2.google.com comp.lang.ada:8508
Date: 2009-09-28T12:18:08+02:00
List-Id: <comp.lang.ada>

Dmitry A. Kazakov wrote:
>> Switching the compiler is a solution we consider as last resort.
> 
> Switching to a never version looks plausible to me.

Our current development environment is based on Debian/Stable. Switching
to GNAT 4.4 requires us to upgrade the environment to Debian
experimental or testing which could introduce some instabilities.
Furthermore, some work is required to do the actual upgrade.

> I was always wondering the rationale behind introducing
> Ada.Real_Time.Timing_Events. The delay statement does the very same thing:

The code I posted was just a small reproducer for the barrier
re-evaluation bug in FSF GNAT 4.3.2. As stated, the problem has nothing
to do with timing events, it also occurs when a "normal" Ada (scheduler)
task is delayed and calls the Wakeup() procedure. Obviously in this
simple example there's no need for timing events or an additional task.