Summary: | internal error in relocate_tls, at ../../binutils-2.25/gold/aarch64.cc:3695 | ||
---|---|---|---|
Product: | binutils | Reporter: | Csaba Osztrogonác <oszi> |
Component: | gold | Assignee: | Han Shen <shenhan> |
Status: | WAITING --- | ||
Severity: | normal | CC: | ccoutant, ian |
Priority: | P2 | ||
Version: | 2.25 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Csaba Osztrogonác
2015-05-19 11:50:16 UTC
I checked it is still valid on trunk: (git hash: 84204ed7) internal error in relocate_tls, at ../../binutils-gdb/gold/aarch64.cc:6637 A tarball containing all the inputs to the link, including the @-file would help. (You can add the -Wl,-t option to the c++ command to get a list of all the files that the linker reads.) If you also add the -v option to the c++ command, it'll show the actual linker command (probably 'collect2'). That would also be helpful. Are you using the --warn-unresolved-symbols option? It looks like this might be a reference to an unresolved TLS symbol. Alternatively, it could be a TLS relocation that refers to a non-TLS symbol, or a TLS symbol in a non-TLS section. The assertion you hit indicates that gold saw a TLS relocation but hadn't created a TLS segment yet. Gold will create a TLS segment whenever it sees a TLS section in an input file (i.e., a section with SHF_TLS set), or when it has any TLS common symbols. Waiting for more data from the reporter. |