This patch series implements full support for dllexport/dllimport attributes
- Adds support for class-wide export/import attributes (PR11170)
- Handles dllexport/dllimport on inline functions and templates
Fixes PR11170, PR13450
Implemented semantics:
- dllexport and dllimport can be applied to functions, static data members and global variables. Both can also be applied to typedefs and enums (without effect) if -fms-extensions is specified, for all other cases the attributes are ignored and a warning is issued. It is an error to apply them to non-static data members.
- dllexport requires a definition. The extern keyword can be used to force a declaration.
- dllimport requires a declaration.
- dllexport exposes the function or variable with its decorated name. a) For C++, this includes name mangling. b) For C or extern "C" functions, this includes platform-specific decoration for the calling convention.
- dllexport takes precedence over dllimport. If both are specified, dllimport is ignored and a warning is issued.
- Classes a) When applied to a class, dllexport or dllimport affect all static and non-static member functions and all static data members, including all non-deleted special members. b) Everything that is accessible to the DLL's client according to C++ access rules is exported (including private data members referenced in inline functions). c) Members can be imported or exported selectively. d) Explicit dllexport/dllimport attributes on members of exported/imported classes are forbidden. e) Base classes of an exported class should be exported. Emits a warning otherwise. (-Wmissing-dllexport) f) Virtual tables and typeinfo follow the emission rules of the Itanium ABI, i.e. for an exported/imported dynamic class with key function, the needed globals are exported/imported. If there is no key function, they are emitted everywhere and are not exported/imported.
- Inline functions a) dllexport can be applied to inline function definitions. The function is always instantiated and exported, presumed to be imported by another program. b) dllimport can be applied to inline function definitions. Such functions can be expanded, but never instantiated.
- Templates a) If a class template is exported, explicit and implicit instantiations are also exported. b) Non-exported/imported class templates can be exported/imported by decorating an explicit instantiation. c) Base classes that are template specializations must be instantiated explicitly to export them. d) If a class is marked as dllexport, any specializations of class templates in the class hierarchy are implicitly marked as declspec(dllexport). This means that class templates are explicitly instantiated and the class's members must be defined.
Implementation notes:
Representing dllexport/dllimport as distinct linkage types prevents using them
on templates and inline functions.
Instead of introducing further mixed linkage types to include linkonce and
weak ODR, the old import/export linkage types are replaced with function
attributes (DLLExport, DLLImport) and an extension to global variables, similar
to how alignment is specified:
@Exp = global i32 1, align 4, dllexport @Imp = external global i32, dllimport
Linkage for dllexported globals and functions is now equal to their linkage
without dllexport. All dllexported entities are decorated with UsedAttr to
ensure their emission. Imported globals and functions must be either
declarations, or definitions with AvailableExternallyLinkage.
In some cases a dllimport/dllexport attribute is ignored. If this happens on
a member of an exported/imported class, we need a way to drop the attribute.
During Sema, when checking such a class, every member is decorated with an
inherited attribute, which allows subsequent dropping. This requires a small
change (or possibly fix?) to table-gen so that the inherited status of an
attribute is preserved when instantiating template attributes.
Open questions/issues:
- With two linkage types removed, should the bitcode mapping of linkage types to integers be adjusted to remove the "holes"?
- Should aliases be exportable/importable? For now an alias is exported if the aliasee is exported.
- Currently dynamic classes with key function cannot have individual virtual members exported as this leads to missing exports for typeinfo.
- The CodeGen tests are extremely slow due to CHECK-DAG, and without CHECK-DAG the tests are very hard to understand because virtual/inline functions are emitted in a different order. Suggestions?
Please note: The uploaded patch is a combination of two git diffs. I prefixed
each one with the project-path from the SVN repo.