Linaro GCC packages don't by default use %gnu_unique_object
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro GCC |
Fix Released
|
High
|
Ramana Radhakrishnan | ||
4.6 |
Fix Released
|
High
|
Ramana Radhakrishnan | ||
4.7 |
Fix Released
|
High
|
Ramana Radhakrishnan | ||
gcc-4.6 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
The example code at http://
Quoting from Ramana's post in the linaro-toolchain mailing list:
I suspect this is a compiler bug around the handling of STB_GNU_
The assembler files on x86_64 from the small testcase have
.type _ZN1AIiE1aE, @gnu_unique_object
while the one in case of ARM doesn't have this.
However my suspicion about the problem is around the fact that GCC in it's build proces emits .type x, @gnu_unique_object to check whether this feature is supported by the GNU assembler. Historically `@' has been a comment character on ARM . So, the compiler doesn't know that GNU_UNIQUE_OBJECT is supported in the assembler and it all falls apart very quickly after that and therefore doesn't generate such code ...
The quickest workaround IMHO is for a new compiler build that is rebuilt with --enable-
Related branches
- Ulrich Weigand (community): Approve
- Andrew Stubbs (community): Approve
summary: |
- Linaro GCC packages don't support %gnu_unique_object on ARM + Linaro GCC packages don't by default use %gnu_unique_object |
Changed in gcc-linaro: | |
assignee: | nobody → Ramana Radhakrishnan (ramana) |
Changed in gcc-linaro: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 4.7-2012.04 |
status: | Triaged → In Progress |
Changed in gcc-linaro: | |
milestone: | 4.7-2012.04 → 4.7-2012.05 |
no longer affects: | gcc-linaro/4.6 |
Changed in gcc-linaro: | |
milestone: | 4.7-2012.05 → 4.7-2012.06 |
affects ARM only