[Bug 251570] Release script passes CPUTYPE variable to both host and target build from MAKE_CONF file

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Feb 5 08:53:09 UTC 2021


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251570

--- Comment #6 from Mark Millard <marklmi26-fbsd at yahoo.com> ---
(In reply to Mark Millard from comment #5)

By the way, for self hosted (not cross builds) I use
the likes of:

# Use of the .clang 's here avoids
# interfering with other C<?>FLAGS
# usage, such as ?= usage.
CFLAGS.clang+= -mcpu=cortex-a72
CXXFLAGS.clang+= -mcpu=cortex-a72
CPPFLAGS.clang+= -mcpu=cortex-a72
ACFLAGS.arm64cpuid.S+=  -mcpu=cortex-a72+crypto
ACFLAGS.aesv8-armx.S+=  -mcpu=cortex-a72+crypto
ACFLAGS.ghashv8-armx.S+=        -mcpu=cortex-a72+crypto

This requires that the the implicit -march= value
to be compatible with the host.

(I've never faced a context with strongly related
-march values, such as a -march=armv8-a host trying
to compile to target -march=armv8.2-a instruction
set extensions that an armv8-a would reject. TARGET
and TARGET_ARCH are not that detailed but determine
what is considered a cross-build in the build
system.)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list