This is an archive of the discontinued LLVM Phabricator instance.

[Sanitizer] Properly use dllimport / dllexport.
ClosedPublic

Authored by mpividori on Jan 23 2017, 3:04 PM.

Details

Summary

I update the headers, so we can change the dllexports to dllimport when defining SANITIZER_IMPORT_INTERFACE , I need these changes for futures diffs fixing Sanitizer Coverage for Windows.

Diff Detail

Repository
rL LLVM

Event Timeline

mpividori created this revision.Jan 23 2017, 3:04 PM
zturner accepted this revision.Jan 23 2017, 3:05 PM

lgtm, this is a standard pattern on Windows.

This revision is now accepted and ready to land.Jan 23 2017, 3:05 PM
rnk edited edge metadata.Jan 23 2017, 3:35 PM

You don't think you should flip it around so consumers of sanitiers_internal_defs.h don't need to define stuff? Instead we'd add SANITIZER_EXPORT_INTERFACE to defines when building sanitizer_common.

@rnk I define it that way, because that interface is internal. We only use SANITIZER_INTERFACE_ATTRIBUTE internally, we don't include that macro in the compiler-rt/include directory.
And we only need to change it to "dllimports" for the internal library: clang-rt_asan_dynamic_runtime_thunk-arch.lib
But now that I think, it would be better to take your approach, and also include SANITIZER_INTERFACE_ATTRIBUTE in the headers provided in the compiler-rt/include directory. So clients, take advantage of the "dllimport" optimization.
Would you agree?

rnk added a comment.Jan 23 2017, 4:18 PM

@rnk I define it that way, because that interface is internal. We only use SANITIZER_INTERFACE_ATTRIBUTE internally, we don't include that macro in the compiler-rt/include directory.
And we only need to change it to "dllimports" for the internal library: clang-rt_asan_dynamic_runtime_thunk-arch.lib

Usually there are more library users than there are libraries, so it's better to define a special macro when compiling the library rather than when consuming the library.

But now that I think, it would be better to take your approach, and also include SANITIZER_INTERFACE_ATTRIBUTE in the headers provided in the compiler-rt/include directory. So clients, take advantage of the "dllimport" optimization.
Would you agree?

I agree, that would be better.

In D29052#654165, @rnk wrote:

@rnk I define it that way, because that interface is internal. We only use SANITIZER_INTERFACE_ATTRIBUTE internally, we don't include that macro in the compiler-rt/include directory.
And we only need to change it to "dllimports" for the internal library: clang-rt_asan_dynamic_runtime_thunk-arch.lib

Usually there are more library users than there are libraries, so it's better to define a special macro when compiling the library rather than when consuming the library.

But now that I think, it would be better to take your approach, and also include SANITIZER_INTERFACE_ATTRIBUTE in the headers provided in the compiler-rt/include directory. So clients, take advantage of the "dllimport" optimization.
Would you agree?

I agree, that would be better.

@rnk Thinking again on this, I think this is appropriate, by default use dllexport, because SANITIZER_INTERFACE_ATTRIBUTE is used on internal headers, not in headers provided to users: which should go in the compiler-rt/include dir.
Internally, we always need to use dllexport, except for some special cases, the dll_thunks and dynamic_runtime_thunks. So, I think is appropriate to use dllexport by default, internally, otherwise, I should add a flag like: BUILDING_LIBRARY, and always include that flag, for all sanitizers, except when building the dll_thunks and dynamic_runtime_thunks, which I think will be confusing.
We always need to dllexport the interface, when the sanitizer is a dll, and when it is a static library (because we use interception).

So, I propose to continue with this approach. In the directory: compiler-rt/include , we can do something different because that headers are independent.
Would you agree?

rnk added a comment.Jan 25 2017, 11:00 AM

Sure, sounds reasonable. In this case we just happen to have fewer library consumers of the exported APIs. The only library consumers are the static thunk libraries.

This revision was automatically updated to reflect the committed changes.