[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug ld/27192] New: conflicting CPU architectures 10/16 error on ARM
From: |
na.vrchol.a.zpet at email dot cz |
Subject: |
[Bug ld/27192] New: conflicting CPU architectures 10/16 error on ARM |
Date: |
Sat, 16 Jan 2021 16:07:58 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=27192
Bug ID: 27192
Summary: conflicting CPU architectures 10/16 error on ARM
Product: binutils
Version: 2.34
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ld
Assignee: unassigned at sourceware dot org
Reporter: na.vrchol.a.zpet at email dot cz
Target Milestone: ---
Created attachment 13124
--> https://sourceware.org/bugzilla/attachment.cgi?id=13124&action=edit
A complete test project for Windows
The armv8-m.base and armv8-m.main architectures cannot be mixed with others
(armv4t through armv7m) when multilinking, even though the entry point is set
(through the provided linker script) to a code compiled under a specific
architecture and --gc-sections should discard unused code for other
architectures, unless unsupported on these new architectures.
I'm on a Windows 10 machine, using bleeding edge toolchain
(https://freddiechopin.info/en/download/category/11-bleeding-edge-toolchain?download=186%3Ableeding-edge-toolchain-200517-64-bit-windows)
with gcc-10.1.0.
See the attached test project with assembler sources (/src), compiled objects
(/out), linker scripts (/script), and linker commands (ld.cmd). In the ld.cmd,
you can change where the toolchain and test project are located, the defaults
are C:/gcc-10.1.0/arm-none-eabi/bin and C:/ld.
--
You are receiving this mail because:
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug ld/27192] New: conflicting CPU architectures 10/16 error on ARM,
na.vrchol.a.zpet at email dot cz <=