Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Oct 2018 10:07:11 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: FYI: SoftIron Overdrive 1000 (aarch64 Cortex-A57) vs. old PowerMac G5 (powerpc64) "Quad Core": a comparison of build times
Message-ID:  <AE6F86CB-1B7F-48B0-92AB-F7AE41BF5B1F@yahoo.com>
In-Reply-To: <EC9E4C02-3291-4D0C-AA62-A18EE98DC841@yahoo.com>
References:  <EC9E4C02-3291-4D0C-AA62-A18EE98DC841@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
[Adding notes about Watts when near 0% idle.]

On 2018-Oct-10, at 2:56 AM, Mark Millard <marklmi at yahoo.com> wrote:

> The following is based on WITHOUT_LLVM_TARGET_ALL=3D and
> powerpc64 has WITH_LIB32=3D while aarch64 does not. In
> both cases system-clang is used to do the buildworld
> buildkernel, although for powerpc64 one would not
> normally install and try to boot and use the result
> for FreeBSD as things are. The builds are self-hosted,
> not cross builds.
>=20
> OverDrive 1000 buildworld buildkernel: a little under 3 hr 17 min.
> G5 "Quad Core" buildworld buildkernel: around         4 hr 53 min (4 =
hr 14 min ignoring lib32 time).
>=20
> The G5 had not started building lib32 (or the kernel) until
> about 3 hr 28 min into its build. aarch64 has no lib32 to
> build. The G5 did not start on the kernel until around 4 hr
> 7 min. So around 4 hr 14 min when not counting lib32's time.
>=20
> powerpc64 is using devel/powerpc64-binutils (or devel/binutils)
> but aarch64 is using lld. (Last I tried lld would not let the
> build complete for powerpc64, if I remember right.) For powerpc64
> the binutils used had been built already.
>=20
>=20
> What was built was (same-in-both part):
> (neither built a bootstrap compiler or
> linker)
>=20
> #WITH_CROSS_COMPILER=3D
> WITH_SYSTEM_COMPILER=3D
> WITH_SYSTEM_LINKER=3D
> #
> WITH_LIBCPLUSPLUS=3D
> WITHOUT_BINUTILS_BOOTSTRAP=3D
> WITH_ELFTOOLCHAIN_BOOTSTRAP=3D
> WITHOUT_LLVM_TARGET_ALL=3D
> #WITH_CLANG_BOOTSTRAP=3D
> WITH_CLANG=3D
> WITH_CLANG_IS_CC=3D
> WITH_CLANG_FULL=3D
> WITH_CLANG_EXTRAS=3D
> WITH_LLD=3D
> WITHOUT_BINUTILS=3D
> WITH_LLDB=3D
> #
> WITH_BOOT=3D
> #
> WITHOUT_GCC_BOOTSTRAP=3D
> WITHOUT_GCC=3D
> WITHOUT_GCC_IS_CC=3D
> WITHOUT_GNUCXX=3D
>=20
>=20
> The variations for what was built between aarch64 vs.
> powerpc64 were:
>=20
> #WITH_LLD_BOOTSTRAP=3D
> WITHOUT_LLD_BOOTSTRAP=3D
>=20
> WITH_LLD_IS_LD=3D
> WITHOUT_LLD_IS_LD=3D
>=20
> WITHOUT_LIB32=3D [This is effectively a comment: aarch64 never has =
lib32]
> WITH_LIB32=3D
>=20
> powerpc64 uses: LOADER_DEFAULT_INTERP=3D4th
>=20
> Also, cortex-a57 used: LDFLAGS.lld+=3D -Wl,--no-threads
>=20
>=20
> Note: My actual powerpc64 builds are via devel/powerpc64-gcc
> and devel/powerpc64-binutils (or devel/binutils), but I've
> not built for aarch64 that way. For powerpc64 I do build
> clang and have clang as cc. (Clang's powerpc64 problems are
> tied to things special for buildworld and buildkernel .)
> Unfortunately, devel/powerpc64-gcc based builds are
> WITHOUT_LIB32=3D because for lib32 it misuses R30 in crtbeginS
> code (vs. the ABI for FreeBSD) and 32-bit code just produces
> core files from the bad dereference that results.
>=20
> Note: The G5 so-called "Quad Core" has 4 cores overall in the
> system but they are evenly split across 2 sockets: 2 dual-core
> processors.

Continuing the comparison of things separated by over
a decade: Watts when (near) 0% idle over sustained
periods during buildworld or poudriere bulk.

PowerMac G5 so-called "Quad Core": around        380 W.
SoftIron Overdrive 1000:           a little under 45 W.

The Overdrive does not have a video card. The G5 has a
video card that is in use as a basic console, not x11
or such.

Other than the video card, the other G5 optional hardware
includes its 16 GiBytes of  RAM and one 480 GByte SSD
appropriate to the older SATA technology. One Ethernet
connection. A USB keyboard.

The OverDrive 1000 has 8 GiBytes of RAM and the hard drive
was replaced by a 1TB Samsung 960 Pro SSD. One Ethernet
connection. Its USB serial console is set up.

At the system level both total to having 4 cores (structured
very differently to get there).

And the Overdrive builds FreeBSD and ports somewhat faster
overall.

Cool.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE6F86CB-1B7F-48B0-92AB-F7AE41BF5B1F>