Slashdot Mirror

← Back to Stories (view on slashdot.org)

LLVM 3.5 Brings C++1y Improvements, Unified 64-bit ARM Backend

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

An anonymous reader writes: LLVM 3.5 along with Clang 3.5 are now available for download. LLVM 3.5 offers many compiler advancements including a unified 64-bit ARM back-end from the merging of the Apple and community AArch64 back-ends, C++1y/C++1z language additions, self-hosting support of Clang on SPARC64, and various other compiler improvements.

3 of 99 comments (clear)

  1. The FSF/GNU folks overreached with GPL v3 ... by Anonymous Coward · · Score: 1, Interesting

    The FSF/GNU folks overreached with GPL v3. They overestimated their importance, pushed a little too hard, and get spanked by Darwin. Both the scientist and the kernel.

    Gcc being displaced was bound to happen. When politics guide engineering the long term is doubtful.

    1. Re:The FSF/GNU folks overreached with GPL v3 ... by Ash+Vince · · Score: 2, Interesting

      The FSF/GNU folks overreached with GPL v3. They overestimated their importance, pushed a little too hard, and get spanked by Darwin. Both the scientist and the kernel.

      Gcc being displaced was bound to happen. When politics guide engineering the long term is doubtful.

      Unfortunately this is a pretty spot on assessment of the situation in my mind.

      Ok, It was annoying that companies were starting to find ways to use OS technology as center pieces in their products and not opening all of their source code to let people tinker with it. The problem their though is that in some cases if they did that then they would reveal too much about things like the underlying hardware that might be under NDA's forced upon them by other companies

      Given enough time this sort of problem might have solved itself as companies slowly moved away from doing business in this way and embracing ideas that ultimately gave them long term benefit (ie: free code), but the GPL3 seemed a crude attempt to force too much change too quickly on business executives who have too much to lose, so are by that point in their careers too conservative.

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
  2. Re:Is there any point continuing GCC's development by boristhespider · · Score: 1, Interesting

    "GNU Fortran is widely used even in high-performance computing because the commercial compilers aren't really better at all (and generally more buggy)."

    While I've certainly encountered (and notified Intel of) bugs in ifort, and more than I'd expect in something that cost the university a pretty parcel of money, I wouldn't even begin to pretend that gfortran is as good for high-performance computing as ifort. Unless you're triggering an ifort bug, and I haven't hit a genuinely serious one since a weird memory cap back in 2005, or using ifort on some esoteric architecture, you are *never* getting better performance out of gfortran optimised code compared to ifort optimised code. They may be equivalent for a lot of operations, but for others ifort is simply a lot better, particularly when tuned to a particular Intel chipset. I use gfortran a lot and I don't have any serious complaints about its optimisation, but ifort's is better.