[PATCH] D34668: llvm-nm: Add suport for symbol demangling (-C/--demangle)
Bob Wilson via llvm-commits
llvm-commits at lists.llvm.org
Thu Jun 29 20:42:26 PDT 2017
> On Jun 29, 2017, at 5:01 PM, Kevin Enderby <enderby at apple.com> wrote:
>
>
>> On Jun 29, 2017, at 1:11 PM, Peter Collingbourne <peter at pcc.me.uk <mailto:peter at pcc.me.uk>> wrote:
>>
>> On Thu, Jun 29, 2017 at 12:17 PM, Rafael Avila de Espindola <rafael.espindola at gmail.com <mailto:rafael.espindola at gmail.com>> wrote:
>> Peter Collingbourne <peter at pcc.me.uk <mailto:peter at pcc.me.uk>> writes:
>>
>> > That would be nice, but it might not be possible until we can drop
>> > backwards compatibility with bitcode files that might not have a symbol
>> > table. This may not happen for a while if I understand Apple's constraints
>> > on backwards compatibility correctly.
>>
>> Do you know if those requirements include llvm-nm and llvm-ar?
>>
>> I have no idea, but I'm copying Kevin and Nick, who might know.
>
> I don’t know the constraints on backwards compatibility when it comes to bitcode files, Nick might know. The guy I would ask here is Bob Wilson who will be back from vacation soon.
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.
Fred and Steven, can you think of anything?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170629/bbdaf6e5/attachment.html>
More information about the llvm-commits
mailing list