[llvm-dev] Question about visibility analysis for whole program devirtualization pass (original) (raw)
Gainullin, Artur via llvm-dev llvm-dev at lists.llvm.org
Thu Nov 30 01:56:23 PST 2017
- Previous message: [llvm-dev] libclang API to access static array initializer
- Next message: [llvm-dev] getCacheSize() implementation (retrieving subtarget id)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi!
I have a question about whole program devirtualization pass. According to my understanding devirtualization is performed only for the classes that have hidden LTO visibility and this visibility is controlled by attributes in the source level or command line options. So visibility analysis is currently performed only in the front-end. But LLVM has LTO internalization pass that uses information from the linker to mark symbols as internal if it is possible. Have you ever considered to make an analysis of visibility at this level (after internalization pass)? Or it is not possible for some reasons?
Best regards, Artur Gainullin
-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171130/81772fb3/attachment.html>
- Previous message: [llvm-dev] libclang API to access static array initializer
- Next message: [llvm-dev] getCacheSize() implementation (retrieving subtarget id)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]