[EXT_EP-10829] Unresolved reference to runtime library function when that function is referenced from asm statement Created: 01/Jun/22 Updated: 01/Jun/22 Resolved: 01/Jun/22 |
|
| Status: | Fixed |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | High |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | Code Generation Tools |
| Internal ID: | CODEGEN-9850 |
| Found In Release: | ARMCLANG_2.0.0.STS |
| Fix In Release: | ARMCLANG_2.1.0.BETA1 ARMCLANG_2.1.0.LTS* |
| Affected Platform/Device: | default |
| Workaround: | If the referenced runtime library function is "_c_int00", the issue can potentially be worked around by adding a -c or -cr option to a linker command file that is incorporated into the link, or by adding a "-Wl,-c" or "-Wl,-cr" to the tiarmclang command that performs the link step.
In other cases, if the referenced runtime library function can be identified, the issue can be avoided by modifying the source code where the runtime library function is referenced, so that the reference does not occur inside an asm() statement. |
| Description |
|
If an application is referencing function defined in a runtime library from an asm() statement in a file that was compiled with -flto, then it is likely that the linker will not resolve the reference to that runtime support function before starting the Link-Time Optimization (LTO) stage of the link. There are two known potential failure symptoms that can occur during the link in this situation:
|