4 ms·

FreeBSD has been using Clang as the default build system for x86/64 since.. 2012? Version 10.0 IIRC. Not sure about mips, sparc, power but think they moved prev

by beezle 7y ago

FreeBSD has been using Clang as the default build system for x86/64 since.. 2012? Version 10.0 IIRC. Not sure about mips, sparc, power but think they moved previously as well?

kevans91 7y ago
powerpc64 switched over in late December; sparc64 never made the switch (unfortunately), and mips will make the switch with the introduction of llvm 10. IIRC powerpc32 is currently using clang with old bfd ld, but lld in llvm 10 may be quickly reaching the point where it's suitable for powerpc32 as well.
- cbmuser 7y ago
  > sparc64 never made the switch (unfortunately) Care to elaborate? We're maintaining sparc64 in Debian Ports and we have smashed quite a number of bugs in the SPARC backend in LLVM. Are there any issues you are seeing?
  - kevans91 7y ago
    This is specifically w.r.t. FreeBSD -- nobody put in the effort to maintain it, so it's removed in head/ as of now. As far as I'm aware, no one had tested sparc64/llvm on FreeBSD either.
    - cbmuser 7y ago
      I see, thanks. I know the NetBSD guys are still working on their sparc64 port.
loeg 7y ago
10.0, 2014 for amd64/i386. Much later for MIPS and Power (within the last year). Sparc was deorbited as part of the GCC4.2.1 retirement effort — no one showed up to implement Sparc support in Clang, and the version of Sparc hardware FreeBSD ran on was extremely obsolete anyway.
- cbmuser 7y ago
  > Sparc was deorbited as part of the GCC4.2.1 retirement effort — no one showed up to implement Sparc support in Clang, and the version of Sparc hardware FreeBSD ran on was extremely obsolete anyway. What's missing for sparc64 in Clang? We have Clang on sparc64 in Debian Ports.
  - loeg 7y ago
    > What's missing for sparc64 in Clang? My memory here is fuzzy because I'm very much not interested in Sparc, but, as far as technical shortcomings: there are integrated-assembler (ias) pieces missing; ld.lld support is extremely incomplete; it's missing a working stack unwinder. If you look for Sparc work in Clang upstream, it becomes obvious that it's not active. The biggest thing missing was interest (and associated time and resources). People have had 6-12 months to step up if they wanted to work on moving platforms off of GCC4.2.1, and unlike for every other tier 2-3 arch formerly on GCC, no one showed up to work on Sparc. > We have Clang on sparc64 in Debian Ports. As in you can compile Clang on sparc (using GCC / binutils as the system compiler), or as in you can actually build Debian for sparc64 using Clang? Here's some more context around missing pieces: https://svnweb.freebsd.org/base?view=revision&revision=354468 https://svnweb.freebsd.org/base?view=revision&revision=35446... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236839 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236839 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239851 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239851
    - cbmuser 7y ago
      > As in you can compile Clang on sparc (using GCC / binutils as the system compiler), or as in you can actually build Debian for sparc64 using Clang? Initially, we were building Clang only. But we're also now building Clang using itself, i.e. a stage2 compiler. There are issues though when building Clang with Clang with Gold as the linker. It works fine with BFD though. We are not building the whole archive with Clang though. But all Rust packages are built on sparc64 as well which uses the LLVM backend. Thanks for the links. I'll look into them. Maybe we find some more bugs than can be fixed on SPARC in LLVM/Clang. Edit: From your first link: > "Contemporary GCC does not build and there is currently no indication that anyone is going to address these issues." That's odd. We're building all GCC versions on Debian/sparc64. It's still a maintained backend in GCC, after all.

by beezle 7y ago

FreeBSD has been using Clang as the default build system for x86/64 since.. 2012? Version 10.0 IIRC. Not sure about mips, sparc, power but think they moved previously as well?

kevans91 7y ago

powerpc64 switched over in late December; sparc64 never made the switch (unfortunately), and mips will make the switch with the introduction of llvm 10. IIRC powerpc32 is currently using clang with old bfd ld, but lld in llvm 10 may be quickly reaching the point where it's suitable for powerpc32 as well.

cbmuser 7y ago
> sparc64 never made the switch (unfortunately) Care to elaborate? We're maintaining sparc64 in Debian Ports and we have smashed quite a number of bugs in the SPARC backend in LLVM. Are there any issues you are seeing?
- kevans91 7y ago
  This is specifically w.r.t. FreeBSD -- nobody put in the effort to maintain it, so it's removed in head/ as of now. As far as I'm aware, no one had tested sparc64/llvm on FreeBSD either.
  - cbmuser 7y ago
    I see, thanks. I know the NetBSD guys are still working on their sparc64 port.

loeg 7y ago

10.0, 2014 for amd64/i386. Much later for MIPS and Power (within the last year). Sparc was deorbited as part of the GCC4.2.1 retirement effort — no one showed up to implement Sparc support in Clang, and the version of Sparc hardware FreeBSD ran on was extremely obsolete anyway.

cbmuser 7y ago
> Sparc was deorbited as part of the GCC4.2.1 retirement effort — no one showed up to implement Sparc support in Clang, and the version of Sparc hardware FreeBSD ran on was extremely obsolete anyway. What's missing for sparc64 in Clang? We have Clang on sparc64 in Debian Ports.
- loeg 7y ago
  > What's missing for sparc64 in Clang? My memory here is fuzzy because I'm very much not interested in Sparc, but, as far as technical shortcomings: there are integrated-assembler (ias) pieces missing; ld.lld support is extremely incomplete; it's missing a working stack unwinder. If you look for Sparc work in Clang upstream, it becomes obvious that it's not active. The biggest thing missing was interest (and associated time and resources). People have had 6-12 months to step up if they wanted to work on moving platforms off of GCC4.2.1, and unlike for every other tier 2-3 arch formerly on GCC, no one showed up to work on Sparc. > We have Clang on sparc64 in Debian Ports. As in you can compile Clang on sparc (using GCC / binutils as the system compiler), or as in you can actually build Debian for sparc64 using Clang? Here's some more context around missing pieces: https://svnweb.freebsd.org/base?view=revision&revision=354468 https://svnweb.freebsd.org/base?view=revision&revision=35446... https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233405 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236839 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236839 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239851 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239851
  - cbmuser 7y ago
    > As in you can compile Clang on sparc (using GCC / binutils as the system compiler), or as in you can actually build Debian for sparc64 using Clang? Initially, we were building Clang only. But we're also now building Clang using itself, i.e. a stage2 compiler. There are issues though when building Clang with Clang with Gold as the linker. It works fine with BFD though. We are not building the whole archive with Clang though. But all Rust packages are built on sparc64 as well which uses the LLVM backend. Thanks for the links. I'll look into them. Maybe we find some more bugs than can be fixed on SPARC in LLVM/Clang. Edit: From your first link: > "Contemporary GCC does not build and there is currently no indication that anyone is going to address these issues." That's odd. We're building all GCC versions on Debian/sparc64. It's still a maintained backend in GCC, after all.