Halo Free!

-={ '<Esc>:read !gcc -march=native -Q --help=target' starts }=-
The following options are target specific:
-mabi=ABI lp64
-march=ARCH armv8-a+crc
-mbig-endian [disabled]
-mbionic [disabled]
-mcmodel= small
-mcpu=CPU
-mfix-cortex-a53-835769 [enabled]
-mfix-cortex-a53-843419 [enabled]
-mgeneral-regs-only [disabled]
-mglibc [enabled]
-mlittle-endian [enabled]
-mmusl [disabled]
-momit-leaf-frame-pointer [enabled]
-moverride=STRING
-mpc-relative-literal-loads [enabled]
-msign-return-address= none
-mstrict-align [disabled]
-msve-vector-bits=N scalable
-mtls-dialect= desc
-mtls-size= 24
-mtune=CPU
-muclibc [disabled]

Known AArch64 ABIs (for use with the -mabi= option):
ilp32 lp64

Supported AArch64 return address signing scope (for use with -msign-return-address= option):
all non-leaf none

The code model option names for -mcmodel:
large small tiny

The possible SVE vector lengths:
1024 128 2048 256 512 scalable

The possible TLS dialects:
desc trad
-={ '<Esc>:read !gcc -march=native -Q --help=target' ends }=-

For the CPU in both -mcpu and -mtune cortex-a53 is/was being deployed. Also worth mentioning is that "-j 4" works EXCEPT when building cmake and for that "-j 3" fixed the fatal issue. Also, also, for some source, cmake for instance,
--build=aarch64-unknown-linux-gnu is/was needs to be passed to configure in order to successfully build. Other than those few cases the new native aarch64-raspi3b+-linux-gnu is more than just fine. I just did a search for aarch64-raspi3b+-linux-gnu and near as I can tell I am the only one using it so
if you're looking to replicate I would advise using aarch64-unknown-linux-gnu instead and keep -march=armv8-a+crc, and -mtune=cortex-a53 and/or -cpu=cortex-a53 for optimizations for the raspberry pi 3b+.

La vida es buena,
Maurice

... No llores por mi tengo vi.
--- GNU bash, version 5.0.0(1)-beta2 (aarch64-raspi3b+-linux-gnu)
* Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)