-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: switch '-mcpu=cortex-a76' conflicts with '-march=armv8-a+sve' switch #2080
Comments
The Aarch64 options are documented separately. You'll find them at https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html.
The regular |
I think the flag is coming from https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/aarch64/fpu/Makefile#l33 I can make your config work if I unset |
From what i've see the flag is only used by the vector math lib. Maybe disabling that fixes it? |
Hi, I was just trying to build a toolchain for RPI5 and bumped into this exact same issue. Thanks. |
After some digging I found the cpu definition in GCC: https://github.com/gcc-mirror/gcc/blob/releases/gcc-13.2.0/gcc/config/arm/arm-cpus.in#L1462 So I'm guessing |
Same issue here - this is what i did:
|
Not sure, but is it about this patch: However is there a option to configure with menuconfig or within the DOTconfig file to override the -march option? |
build.log.gz (~35MB uncompressed)
dot_config.txt
Hey there,
Trying to compile a 64-bit toolchain for the new RPi 5 (
aarch64-rpi5-linux-gnu
). I'm not sure how the official one is set up, but I would be happy with anything with-mcpu=cortex-a76
. Except, when I attempt to do just that, my build fails withI.e. it looks like something is attempting to set
-march=armv8-a+sve
. Not sure how or why, assve
isn't even one of the documented extensions for ARM (although it's definitely an ARMv8 extension, and I read it's been supported in GCC for a while - so not completely sure what's going on here). This might have something to do with #963.I have also tried to build with
CT_ARCH_ARCH="armv8.2-a"
, with and without also specifying the CPU. When still specifying the CPU, the wrong-march
flag gets set again. When not specifying the CPU however the build succeeds. (But I haven't tested it just yet.)If this is something that's happening inside crosstool-NG, it should imho be fixed, as setting the CPU is in my view preferable - as it's a relatively high-level information encompassing architecture, extensions, etc, then leaving the compiler to expertly decide how to configure itself to emit the best possible code.
If not, could you help me understand when and how this happens, so that I can contact the relevant people?
Thank you!
The text was updated successfully, but these errors were encountered: