6 ms·

The M3 Max laptops can cross-build FreeBSD at a fraction of the time of the ThinkPad, being at around 791 seconds for `make -j17` versus the T14s being at 3210

by winocm 2y ago

The M3 Max laptops can cross-build FreeBSD at a fraction of the time of the ThinkPad, being at around 791 seconds for `make -j17` versus the T14s being at 3210 seconds (with `make -j12`) according to the post above. No idea about power consumptions. It still scares me.

redundantly 2y ago
Do you have more details or a source on this? I'd like to learn more about the build process and timings.
- winocm 2y ago
  Sure. I basically did the following on trunk: $ CPP=/usr/bin/clang MAKEOBJDIRPREFIX=/private/var/tmp/obj ./tools/build/make.py TARGET=arm64 TARGET_ARCH=aarch64 --host-compiler-type clang --debug -j17 --clean buildworld You probably can follow build(5) from FreeBSD hosts instead. NetBSD is similar, but you need to edit `tools/llvm/Makefile` and make sure that you use the following target for `support-modules` instead: support-modules: module-test.cpp Makefile - if ${HOST_CXX} -stdlib=libc++ -c -fmodules -fcxx-modules -fmodules-cache-path=./module.cache \ - ${.CURDIR}/module-test.cpp 3> /dev/null 2>&1; then \ - echo HOST_SUPPORTS_MODULES=yes > ${.TARGET}; \ - else \ - echo HOST_SUPPORTS_MODULES=no > ${.TARGET}; \ - fi + # Just don't use modules pre for C++20 targets. Some compilers cannot support them. + echo HOST_SUPPORTS_MODULES=no > ${.TARGET}; You can further speed up NetBSD builds by editing `share/mk/bsd.sys.mk` and removing the workaround for SunPro's cc. The repeated invocation of /bin/mv for each object file really does add up. I have not tried cross builds of OpenBSD from other operating systems.
  - winocm 2y ago
    Word of warning, I ended up getting a lot of strange compiler segfaults within xgcc when using when using `MKGCC=yes` instead `MKLLVM=yes` with NetBSD, specifically with floating point heavy code. I never did end up finding out why that happens.
Sardtok 2y ago
One is $1000 and the other is around $3000. So performance per dollar looks about right.
- wslh 2y ago
  Not only performance per dollar but also battery duration/consumption.
  - gjsman-1000 2y ago
    [flagged]
    - sgerenser 2y ago
      Not so on the M3 generation (nor the newer M4s). M3 Pro was particularly hobbled in this regard with only 6 performance cores vs 10 on the Max.
      - liprais 2y ago
        my m4 pro has 10 p cores as m4 max has ,get your facts right at least.
        microtonal 2y ago
        You can get the M4 Max with 12 performance cores.
        deleted 2y ago
        [deleted]
        sgerenser 2y ago
        Comparing unbinned to unbinned, you get 10 P cores on the M4 Pro and 12 on the M4 Max. Regardless the original comment was regarding the M3 series, where there was an even larger difference between the M3 Pro and M3 Max (6 vs 10 P cores).
    - 2y ago

by winocm 2y ago

redundantly 2y ago

Do you have more details or a source on this? I'd like to learn more about the build process and timings.

winocm 2y ago
Sure. I basically did the following on trunk: $ CPP=/usr/bin/clang MAKEOBJDIRPREFIX=/private/var/tmp/obj ./tools/build/make.py TARGET=arm64 TARGET_ARCH=aarch64 --host-compiler-type clang --debug -j17 --clean buildworld You probably can follow build(5) from FreeBSD hosts instead. NetBSD is similar, but you need to edit `tools/llvm/Makefile` and make sure that you use the following target for `support-modules` instead: support-modules: module-test.cpp Makefile - if ${HOST_CXX} -stdlib=libc++ -c -fmodules -fcxx-modules -fmodules-cache-path=./module.cache \ - ${.CURDIR}/module-test.cpp 3> /dev/null 2>&1; then \ - echo HOST_SUPPORTS_MODULES=yes > ${.TARGET}; \ - else \ - echo HOST_SUPPORTS_MODULES=no > ${.TARGET}; \ - fi + # Just don't use modules pre for C++20 targets. Some compilers cannot support them. + echo HOST_SUPPORTS_MODULES=no > ${.TARGET}; You can further speed up NetBSD builds by editing `share/mk/bsd.sys.mk` and removing the workaround for SunPro's cc. The repeated invocation of /bin/mv for each object file really does add up. I have not tried cross builds of OpenBSD from other operating systems.
- winocm 2y ago
  Word of warning, I ended up getting a lot of strange compiler segfaults within xgcc when using when using `MKGCC=yes` instead `MKLLVM=yes` with NetBSD, specifically with floating point heavy code. I never did end up finding out why that happens.

Sardtok 2y ago

One is $1000 and the other is around $3000. So performance per dollar looks about right.

wslh 2y ago
Not only performance per dollar but also battery duration/consumption.
- gjsman-1000 2y ago
  [flagged]
  - sgerenser 2y ago
    Not so on the M3 generation (nor the newer M4s). M3 Pro was particularly hobbled in this regard with only 6 performance cores vs 10 on the Max.
    - liprais 2y ago
      my m4 pro has 10 p cores as m4 max has ,get your facts right at least.
      - microtonal 2y ago
        You can get the M4 Max with 12 performance cores.
      - deleted 2y ago
        [deleted]
      - sgerenser 2y ago
        Comparing unbinned to unbinned, you get 10 P cores on the M4 Pro and 12 on the M4 Max. Regardless the original comment was regarding the M3 series, where there was an even larger difference between the M3 Pro and M3 Max (6 vs 10 P cores).
  - 2y ago