Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#59430 - llvm-nm does not accept bitcode files (version compare mismatch)
Attached to Project:
Arch Linux
Opened by Heiko Eißfeldt (hexcoder) - Monday, 23 July 2018, 22:30 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 26 July 2018, 18:03 GMT
Opened by Heiko Eißfeldt (hexcoder) - Monday, 23 July 2018, 22:30 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 26 July 2018, 18:03 GMT
|
DetailsDescription: Running llvm-nm on a bitcode file gives an error message
instead of the expected symbols listing. The error message is: llvm-nm: files.bc Invalid function argument type (Producer: 'LLVM6.0.1' Reader: 'LLVM 6.0.1') Please note the extra space after 'LLVM' in the Reader version string. Additional info: * package version: 6.0.1-1 Steps to reproduce: Steps to reproduce: 1. compile some source to bitcode object file 2. run llvm-nm on bitcode object file |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Thursday, 26 July 2018, 18:03 GMT
Reason for closing: Works for me
Additional comments about closing: Based on a private email, this only happens with a custom LLVM pass (where the issue probably lies).
Thursday, 26 July 2018, 18:03 GMT
Reason for closing: Works for me
Additional comments about closing: Based on a private email, this only happens with a custom LLVM pass (where the issue probably lies).
llvm-nm_bug
You'll need to provide a full reproduction example, since I can't repro with something like "int main() {return 0;}".