Back to bug 2119383
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2022-08-18 13:45:49 UTC | Pool ID | sst_pt_gcc_glibc_rhel_7 | |
| Red Hat One Jira (issues.redhat.com) | 2022-08-18 13:51:17 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-131417 | |
| Nick Clifton | 2022-08-18 16:05:32 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Keywords | Bugfix, Triaged | |||
| Doc Text | Cause: When the LLVM compiler generates object files intended for secondary compilation via LTO it uses an internal file format rather than ELF. Consequence: Tools which expect ELF format input files, eg the linker, nm, readelf, etc, will fail to recognise LLVM bitcode files. Workaround (if any): For most tools adding the command line option --plugin=LLVMgold.so will solve the problem. The readelf program does not support this option however, so an alternative is to use the llvm-bcanalyzer program. Result: Using the workarounds resolves the problem. | |||
| Status | NEW | CLOSED | ||
| Resolution | --- | WONTFIX | ||
| Last Closed | 2022-08-18 16:05:32 UTC | |||
| Jesus Checa | 2022-08-24 07:07:16 UTC | Depends On | 2120959 | |
| Mark O'Brien | 2023-07-18 14:16:41 UTC | Pool ID | sst_pt_glibc_rhel_7 | sst_pt_gcc_rhel_7 |
Back to bug 2119383