On Wed, Jun 20, 2001 at 02:16:35PM +0300, mulix wrote:
> On Wed, 20 Jun 2001, Adi Stav wrote:
> 
> > I haven't tried, but if I understood correctly the frontend was hardly
> > changed, while the C++ frontend was almost rewritten from scratch. Probably
> > Gnome compilation will be affected less strongly than KDE. At work I tried
> > to recompile some of our C libraries (works fine) and C++ librariess
> > (tons of errors, fails). I don't know whether the C++ problems in KDE's case
> > and in my own expriments' case were GCC's fauilt or that the code was wrong,
> > though.
> 
> much more likely that it's the code's fault. g++ (and libstdc++v3)
> conform much better to the c++ standard, which means it will not accept
> code it might've accepted in the past.
> 
> on behalf of the gcc developers, if you think you found a bug in gcc,
> reconsider. one of the critical release criteria of gcc was that there
> will be _no_ regressions from gcc-2.95.2. code that compiles with
> gcc-2.95.2 and no longer compiles with gcc-3.0 is probably not standards
> conforming (enough). consult with someone who really knows the language.
> try other (standards conforming!) compilers. only then, if you are sure
> you found a bug, use the 'gccbug' shell script to report it.

So I thought. Afterall, the C standard is a much more forgiving (ok ok, 
unsafe) than the C++ standard, plus there's less to conform to.

I wonder how long it'd take for GCC 3.0 to be considered a safe C++
compiler to ship alone for stable distributions, though.

> re compiling the kernel with gcc-3.0: you can do it, but it's not
> recommended. even if the compilation succeeds (i dont think it does, at
> the moment, some problem with builtin functions) there is a whole slew
> of arcane magic and black wizardry that can go wrong, if the compiler
> does something differently than what it used to do. you might get a
> kernel that runs, but silently trashes your data. in other words, try
> it, but if it breaks, you get to keep both pieces...

Considering that the GCC 3.0 i386 backend was rewritten, I am genuinely 
surprised to hear that it compiled at all.

Again, I'm wondering how long it'd take for GCC 3.0 to be considered 
safe for the kernel. I'll place my conservative bet of 18 months, at 
least.

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to