[PATCH] D34668: llvm-nm: Add suport for symbol demangling (-C/--demangle)

Steven Wu via llvm-commits llvm-commits at lists.llvm.org
Fri Jun 30 11:36:37 PDT 2017


I can't think about anything that is really going be broken if you drop support for old bitcode file in llvm-nm and llvm-ar. I also like the idea to make them smaller.

The only concern I have is if we drop support in llvm-nm, we lost the simple tool to quickly inspect the symbol take from old bitcode file. That can be disruptive for some workflow because unfortunately I sometimes need to debug old bitcode files. As long as there is a replacement workflow for inspecting symbol table from old bitcode file before we drop support, I can't think about anything against this idea now.

Steven

> On Jun 30, 2017, at 11:13 AM, Rafael Avila de Espindola <rafael.espindola at gmail.com> wrote:
> 
> Bob Wilson <bob.wilson at apple.com> writes:
> 
>> Am I right that you’re suggesting that llvm-ar and llvm-nm could support only newer bitcode files that have symbol tables, while other uses of old bitcode files (e.g., for LTO) would continue to work? I can’t think of anything offhand that would be broken by that.
> 
> That is correct. Only llvm-nm and llvm-ar would change. llvm-nm would be
> unable to print symbols from old bitcode files. llvm-ar would still
> create an archive, but the old bitcode members would not contribute to
> the archive symbol table.
> 
> Cheers,
> Rafael



More information about the llvm-commits mailing list