From: Anh Vo <anhvofrcaus@gmail.com>
Subject: Re: GNAT stuck, any idea on how to diagnose it?
Date: Sun, 14 Sep 2014 15:56:35 -0700 (PDT)
Date: 2014-09-14T15:56:35-07:00 [thread overview]
Message-ID: <12b0f080-6063-4d56-b3f5-c7c9375cac49@googlegroups.com> (raw)
In-Reply-To: <slrnm1c37u.nrc.lithiumcat@nat.rebma.instinctive.eu>
On Sunday, September 14, 2014 2:47:47 PM UTC-7, Natasha Kerensikova wrote:
> Hello,
>
> On 2014-09-14, Brad Moore <brad.moore@shaw.ca> wrote:
> > On 2014-09-14 8:49 AM, Dmitry A. Kazakov wrote:
> >> On Sun, 14 Sep 2014 09:21:18 +0000 (UTC), Natasha Kerensikova wrote:
>
> Now a secondary question would be, how long is it reasonable to let GNAT
> run before assuming it won't terminate ever?
It depends on size of the code in question. For normal case if gnat1 occupies close to 99% CPU in 30 seconds or more, that means the compiler runs away. I would submit a bug report.
A. Vo
next prev parent reply other threads:[~2014-09-14 22:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 9:21 GNAT stuck, any idea on how to diagnose it? Natasha Kerensikova
2014-09-14 11:59 ` Georg Bauhaus
2014-09-14 14:49 ` Dmitry A. Kazakov
2014-09-14 15:21 ` Brad Moore
2014-09-14 21:47 ` Natasha Kerensikova
2014-09-14 22:56 ` Anh Vo [this message]
2014-09-15 7:15 ` Dmitry A. Kazakov
2014-09-14 21:45 ` anon
2014-09-15 7:25 ` Dmitry A. Kazakov
2014-09-15 9:56 ` anon
2014-09-15 7:16 ` Natasha Kerensikova
2014-09-15 7:26 ` Jeffrey Carter
2014-09-14 17:45 ` Robert A Duff
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox