https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251570
Mark Millard <marklmi26-f...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marklmi26-f...@yahoo.com
--- Comment #5 from Mark Millard <marklmi26-f...@yahoo.com> ---
My files analogous to src.conf or src-env.conf for
cross building (amd64->???) via system clang have
lines like:
XCFLAGS+= -mcpu=cortex-a72
XCXXFLAGS+= -mcpu=cortex-a72
# There is no XCPPFLAGS but XCPP gets XCFLAGS content.
ACFLAGS.arm64cpuid.S+= -mcpu=cortex-a72+crypto
ACFLAGS.aesv8-armx.S+= -mcpu=cortex-a72+crypto
ACFLAGS.ghashv8-armx.S+= -mcpu=cortex-a72+crypto
I've only experimented with such specific control for
cortex-a7, cortex-a53, cortex-a57, and cortex-a72, i.e.,
the armv7 and aarch64 systems that I've had access to,
not targetting powerpc64, powerpc, or amd64.
-mcpu= implicitly picks the matching -march= value and
also sets the -mtune= value. The A53, A57, and A72
share the same -march= (armv8-a if I remember the command
line notation correctly) but can have very different
tuning. (In part this is because the A53 does not do many
things that the architecture allows, such as: it only
executes in order.)
I've not dealt with using the release script in years,
so I make no specific claims for that context. And even
for just use with make, the above probably steps into
"you are on your own" space. But at the time I adopted
the technique, I did not find any way to avoid that
status while doing the targeting via the style of build.
I've not had any troubles attributed to the above.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
