From: Simon Wright <simon@pushface.org>
Subject: Re: Reporting GNAT bugs
Date: Tue, 28 Oct 2014 21:45:49 +0000
Date: 2014-10-28T21:45:49+00:00 [thread overview]
Message-ID: <lyioj3x3zm.fsf@pushface.org> (raw)
In-Reply-To: m2ov1n$82u$1@speranza.aioe.org
Victor Porton <porton@narod.ru> writes:
> If I found a serious GNAT bug, is it enough to report it at
> https://gcc.gnu.org/bugzilla/ ?
>
> Or should I also ping someone so that the bug would not be lost and
> fixed quickly?
If the bug can be reproduced in GNAT GPL, send it to report@adacore.com
(possibly as well as at the GCC bugzilla; that way the rest of us get to
see it).
I've had quite good experiences at Bugzilla with bugs that affect the
build/ACATS, especially in the early stages of the release
process. Others not so much (I had a minor one about gnatmake not
showing the switches it passes to ranlib, which got improved to the
point of acceptance but then never got implemented).
The people who will fix the bug are (almost?) all at AdaCore. GNAT GPL
bugs sent to report@adacore.com may end up being fixed in their working
sources (there have been a couple of reports of this recently), and if
you are supported you will be able to get a wavefront release if you
need one. Otherwise, you get to wait for the next release of GNAT GPL
or the next major GCC release (now 4.10).
next prev parent reply other threads:[~2014-10-28 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 20:41 Reporting GNAT bugs Victor Porton
2014-10-28 20:59 ` Martyn Pike
2014-10-28 21:45 ` Simon Wright [this message]
2014-10-28 23:56 ` Victor Porton
2014-10-29 6:27 ` Simon Wright
2014-10-29 10:18 ` Brian Drummond
2014-10-29 22:29 ` Victor Porton
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox