Mail Archives: djgpp/2000/06/10/02:01:02
> From: zargon AT hotmail DOT vom (Zargon)
> Newsgroups: comp.os.msdos.djgpp
> Date: Fri, 09 Jun 2000 20:33:19 GMT
>
> >> >>egcs-291.60
> >> >
> >> >Try upgrading to GCC 2.95.2 and DJGPP 2.03.
> >>
> >> That sounds suspiciously like a downgrade to me!
> >
> >Sorry, I fail to see how so: the version you are using sounds like it's
> >version 2.91.60, so 2.95.2 is certainly newer.
>
> No, egcs doesn't seem to use the same numbering as gcc.
What EGCS? There is no EGCS anymore, it was renamed back to GCC, when
the EGCS team got the responsibility of maintaining the mainstream GCC
distribution.
If you mean PGCC, then I suggest to drop it: it's buggy, and is known
not to work in some important cases. AFAIK, it's also not maintained
anymore (what is the time stamp on the compiler binaries, btw?).
> In any case, I'd rather use egcs with its optimizations and more
> advanced and more standard-conforming C++ support than use stock gcc.
There's nothing more advanced about EGCS or PGCC anymore. There are
more bugs, but you probably don't want them ;-)
> >I don't see anything in this list that doesn't work in GCC 2.95.2. Did you
> >actually try it and saw some specific problems?
>
> No, but IIRC stock gcc:
> * Lacks Pentium optimizations, unlike egcs;
> * Has quirks with C++ exceptions, unlike egcs;
> * Has severe linkage problems with C++ templates, which egcs IIRC
> fixes with a "template repository"; and
> * Does not support namespaces, with some variants *crashing* if they
> see namespace keywords, while egcs supports namespaces.
You are *way* out of date with these items, they are all fixed in
current versions of GCC, certainly if you actually mean EGCS, and even
if you mean PGCC.
Simply stop using this version of the compiler, it might as well be
*the* reason for your problems with Allegro. None of the DJGPP
developers uses that compiler version, which alone should be enough
for you to drop it.
- Raw text -