System header warning exemptions and delta debugging don't mix well

2005-09-24 Thread dank
Short story: To make delta debugging more useful, gcc's STL system headers should all compile without warnings at the highest error checking level without the use of hardcoded warning suppressions in the compiler based on whether the code is in a system header or not (see http://gcc.gnu.org/ml/gcc-

re: c++ performance regressions in gcc > 2.95.3

2005-08-06 Thread dank
Anthony wrote: > We observed that certain large C++ applications perform worse > in gcc-3.x and gcc-4.x than they did in gcc-2.95.3. > On the theory that at least some of the cause > would show up in microbenchmarks, we tried running > bench++ with both old and new toolchains. > ... > http://www.ci

re: GCC 4.0.1 - iostream: No such file or dir....

2005-08-06 Thread dank
Chris Garrett <[EMAIL PROTECTED]> wrote: > main.cpp:5: error: 'cout' was not declared in this scope This question should have been sent to gcc-help, not here. But as long as I'm answering: It's std::cout now, according to the C++ standard. If you want to compile old code that wasn't aware of std

Re: Symbol versions for inlined symbols

2005-07-30 Thread dank
> You may wish to read the proceedings from this year's GCC summit, where > another solution was presented by some gentlemen from Intel. For > various reasons, symbol versioning is not a useful solution to this > problem. > > No one objected to their solution in principle, AFAICT, although there >

re: Large, modular C++ application performance ...

2005-07-30 Thread dank
MM wrote in http://go-oo.org/~michael/OOoStartup.pdf: "... not one slot was overridden by an implementation method external to the implementing library." Hmm. For some reason that reminds me of the 'final' keyword which is periodically proposed (e.g. http://gcc.gnu.org/ml/gcc/2004-02/msg01483.htm

Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux crosscompiler...

2005-07-28 Thread dank
ddaney wrote: > I have a a mipsel-linux cross compiler (gcc-3.4.3/binutils-2.16.1) > and whenever I compile even the simplest hello-world.c libgcc_s.so is linked. Just curious -- how did you build your cross-compiler? Do toolchains built by crosstool have this problem? (I'm away from home, or I'd

Blogging the gcc summit

2005-06-22 Thread dank
Dunno who else is doing it, but I'm trying to do a realtime diary of the gcc summit for the benefit of those who couldn't come. It's at http://kegel.com/gcc/summit2005.html I don't promise that it's legible or useful, but it might give some of the flavor, at least.