Slashdot Mirror


GCC 3.4.0 Released

AaronW writes "While checking the GCC website I saw that GCC version 3.4 was officially released on April 18th. Version 3.4 includes numerous changes and enhancements, including better optimization, and the ability to build a profiled version of gcc which is 7.5-11% faster on i386 hardware. Be kind and please use one of the mirror sites."

7 of 68 comments (clear)

  1. Profiling shared libraries by wowbagger · · Score: 4, Interesting

    Has the ability to profile shared libraries been fixed? I have tried to do this, and even if you compile a shared library with -pg, and specify it in the LD_PROFILE environment variable, the resulting profile file cannot be processed by gprof V2.4 - instead you get "error: unsupported profile revision 131,071"

    I *really* need to profile a shared library, and building it as a staticly linked executable is not an option.

  2. GCJ by InsaneCreator · · Score: 3, Interesting

    Could someone explain how well does the gcj Java compiler work? I hear that AWT and Swing are not really usable, so how well does it work with SWT or maybe even wxWidgets?

    I'm currently in the process of choosing the language/tools for a cross platform app (open source, of course) and I've narrowed the selection down to Java+gcj and c++. Native executables & widgets are a must, since my target audince most likely won't have a JVM installed.

  3. Re:Broken C++ ABI ... again by Dr.Dubious+DDQ · · Score: 4, Interesting

    Well, if you want to be technical about it, it's not "Broken" C++ ABI, but a "Finally fixed, even though that makes it no longer bug-for-bug compatible with older GCC C++ ABI's"...

    As I understand it, they've been working towards a more standards compliant C++ implementation, and that's why the binary compatibility gets lost.

    I am, though, hoping that there was NOT a loss of compatibility between the 3.3.3 that I'm using now and the 3.4 series. Will find out once I clean off enough disk space to finish compiling up slack packages for myself...

  4. PCH and auto* by greppling · · Score: 2, Interesting

    Has anybody done the work to setup PCH in a project built with the standard GNU Makefile tools autoconf/make/header? I tried it once, but didn't see a good solution to get the dependencies right. Of course, genuine support for it by automake would be great.

  5. Idle curiosity by bhima · · Score: 2, Interesting

    OK I know this is just idle curiosity but I think a general comparison between Microsoft's new offering, Borland's Free command line tools, Open Watcom and GCC might be interesting.

    --
    Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    1. Re:Idle curiosity by CoolGuySteve · · Score: 2, Interesting

      Don't forget ICC. If GCC could even begin to compete somewhat with the Intel compilers, the scientific community would probably take notice. From the experiences of the programmers and students at our department, Intel stuff is really buggy and wastes a lot of time with things like 'Internal Compiler Errors' and examples in the documentation that either don't work or don't compile.

      Maybe IFC and ICC work better if you're not doing anything complicated or using exotic hardware, they probably weren't tested much on Itanium systems with 64GB of ram.

  6. This may be a stupid question, but... by Anonymous Coward · · Score: 1, Interesting

    ...where does one get the PGP/GPG public key necessary to validate the gcc-3.4.0.tar.bz2.sig file? I've searched all over the gcc.gnu.org website and I cannot find it.