Re: A bug in gnat/gcc 3.3.3?

["Adrian Hoe" <byhoe@greenlime.com>]

Florian Weimer wrote:
> * Ludovic Brenta:
>
> >> Yes! 3.4 is currently the best option. 3.15 is old, 3.3 is buggy
and
> >> 4.0 is still fighting with the tree-saa extentsion.
> >
> > I differ with this.  The quality of GCC 3.4 is similar to, but not
> > significantly better than that of GNAT 3.15p.  Also, 3.4 is much
> > slower and memory-hungry than 3.15p (it may or may not matter to
you
> > but it's a fact).
>
> But this comparison is not fair because you are backporting fixes to
> GNAT 3.15p.  No one is doing this for GNAT in GCC 3.4. 8-)
>
> Due to the NPTL problem, plain GNAT 3.15p is probably not so useful
> for many people with recent GNU/Linux distributions.

Could you elaborate further your last statement? Why do you think
gnat3.15p is not so useful with recent GNU/Linux distribution?

Also, does gnat3.15p work well with gcc3.3.3?

If I'm going to bootstrap gnat 3.15p with gnat/gcc3.3.3, wouldn't the
buggy 3.x affect the compilation? Has anyone tried to bootstrap
gnat3.15p with gnat/gcc3.x before?

Honestly, I have compiled thousands of Ada code (previously compiled
with gnat3.15p on Caldera and SuSE) with gnat/gcc 3.3.3 and had no
problems and they run well until this bug box appeared when I tried to
compile dgate.adb. I had no problem compiling GtkAda-2.2.1 at all. And
the GtkAda installed and works perfectly on my SuSE 9.1pro.

Another issue is that gnat3.15p has been out there for a long time and
seems no upgrade from gnat/libre. Do we consider gnat/gcc 3.x an
upgrade?

Adrian Hoe