Slashdot Mirror

← Back to Stories (view on slashdot.org)

GCC 5.2 Released

Posted by Soulskill on from the onward-and-upward dept.

AmiMoJo writes: The release of GCC 5.2 brings lots of bug fixes and a number of new features. The change list is extensive, featuring improvements to the C compiler, support for new languages like OpenACC, improvements for embedded systems, updates to the standard library and more.

6 of 91 comments (clear)

  1. People still use GCC? by Anonymous Coward · · Score: 1, Insightful

    I switched to clang long ago, haven't really looked back except to read Stallman's sad rantings

    1. Re:People still use GCC? by fahrbot-bot · · Score: 5, Insightful

      Why would I waste my time explaining things to idiot morons?

      Knowledge should be passed along, not hoarded. Everyone is at a different place on the learning curve. In practical terms, that means everyone is an idiot moron with respect to someone else - or, in your case, obviously many others.

      --
      It must have been something you assimilated. . . .
  2. autotools is no fun by Bruce+Perens · · Score: 5, Insightful

    I've been configuring a toolchain for Algoram's programmable radio transceiver, which has a SmartFusion 2 containing a Cortex M3. Until today, I've been working with GCC 5.1. Building GCC for cross-compilation on a no-MMU, no-FP processor and a software platform that doesn't support shared libraries isn't trivial, though it should be. GCC has many configure scripts, one for each library that it builds and at least one for the compiler. You run across many configure issues which are difficult to debug. For example, the configure file, a macro-expanded shell script, doesn't have source code line numbers from its configure.ac file. Error messages do not in general indicate the actual problem, and are difficult to trace. Figuring out what to fix is far from trivial. I ended up not being able to use multilibs (which would have allowed me to build for FP processors like Cortex M4F as well), couldn't link in ISL, couldn't build libjava.

    Some of these are beginner problems - I'm new to building cross-toolchains and have avoided autotools as much as possible before this project. But not all of them.

    One would think that we could build a better system today than such voluminous M4 and shell. Perhaps basing it on a test framework might be the right approach.

    --
    Bruce Perens.
  3. Re:I hope they fixed the size issue. by Lisandro · · Score: 4, Insightful

    The compiler? Why would you want to run that on an embedded system?

  4. Re: Try Stack Overflow and --synclines by Bruce+Perens · · Score: 4, Insightful

    This isn't really a problem for StackOverflow. It's a problem for the developers of GCC and its libraries, and a policy problem for the overall GNU project in that Autotools is IMO too much of a mess to live, and is a barrier to participation as it stands. That's why I talk about it here instead of just submitting it as a bug report.

    I would like to see someone come up with an alternative. That alternative is not CMake or Scons, etc., because those are build systems rather than systems that probe a platform for fine differences in the programming environment and produce a set of macro switches as output.

    --
    Bruce Perens.
  5. Re:5.2 by Anonymous Coward · · Score: 0, Insightful

    Why should I give a shit? llvm+clang is better than Stallman's toe jam.