[Windows] Fix Registry static data members not exported by extract_symbols.py in static builds with plugin support (#163391) When building LLVM statically (without BUILD_SHARED_LIBS) on Windows with LLVM_EXPORT_SYMBOLS_FOR_PLUGINS=ON, external plugins cannot register through llvm::Registry<clang::PluginASTAction> because: Static data members (Head, Tail) are filtered out during symbol export by extract_symbols.py because they don't match the function signature patterns that the script looks for. This patch fixes the issue by adding pattern matching to extract_symbols.py to recognize and export Registry static data members. Note: When LLVM is built with /Zc:dllexportInlines-, inlined functions aren't exported as symbols, and the plugin must also compile with /Zc:dllexportInlines- to inline them instead of referencing non-exported symbols. Fixes #163367
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.