I finally found the bug: its name is "g++"

George Garvey tmwg-gcc@inxservices.com
Thu Sep 6 13:31:00 GMT 2001

On Thu, Sep 06, 2001 at 07:06:57PM +0200, Carlo Wood wrote:
> I started to use C++ around 2.96 (RedHats) and have since
> reported dozens of bug reports - which indeed have taken a lot
> of my time.

   Been using it a lot longer than that. 3 is needed, but I total
understand Markus. Been feeling about the same, and considering the same
   There's a problem with the open list: one watches all the fun with new
development, while one is having problems even using the compiler. Can't
compile several needed C libraries with 3, must use 2.95 (openSSL comes to
mind). Can't use -fomit-frame-pointer any more (the amount of time to go
through makefiles where that was hard coded is a ridiculous waste).
   Really don't want to remember all the problems and the amount of time
that has been spent dealing with them in the last few months.
   Joined this list hoping that it was true that bug reports were desired,
as was stated in one of the manifestos I read. Not convinced that's true
for all the developers (although its obviously true for many -- but doesn't
mean the bugs I report will get looked into). Have just about abandoned
that idea. Now read it to see what's going on, because there's usually
insufficient notice in change documents to know for sure what's changed
between releases except at a very high level -- and the change logs are too
low a level and too time consuming to understand.
   Have filed bug reports, but not as often as needed because of the time
required just to find out what the problem is this time -- then can't find
a way to trim the problem down to make it easy enough to replicate. Can't
believe I'm the only one who can't compile openSSL right now with 3, for
   At this point, I've not made a decision about whether to switch away
from the GNU compiler. Mark has been trying to get something done about it,
need to see how that works out. Assume that using a commercial product will
just bring different hassles, from the experience of the past with C/C++
compilers. That's actually what got me to swtich to GNU in the first place.
Now the problems seem very familiar. Either way, I end up paying for it
with time. But its still a tough decision to deal with.
   Do I pay money to have problems, or pay nothing to have problems and
possibly be ignored as well? Don't know right now.
   Don't really understand what's going on with the developers well enough
to even make the decision. Can't really get a grip on the over all point of
view on the subject from watching from the outside. But the situtation
right now is very discouraging.

More information about the Gcc-bugs mailing list