[LLVMbugs] [Bug 9078] New: Plug-in mechanism broken on Windows

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=9078

           Summary: Plug-in mechanism broken on Windows
           Product: clang
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: John.Thompson.JTSoftware at gmail.com
                CC: llvmbugs at cs.uiuc.edu


Created an attachment (id=6066)
 --> (http://llvm.org/bugs/attachment.cgi?id=6066)
llvm side

In loading a Windows plug-in DLL, the DLL will have it's own copy of the clang
library code and data, such that the plug-in registry node list ends up in the
DLL and not the Clang executable's data space.

Making the Clang library a DLL might make it work.  Alternatively, if nothing
in clang references changed static data, perhaps it might work if the plug-in
can get to the data it needs by the references given to it.  The plug-in still
needs some way to get the registry info into clang, perhaps by Clang calling a
function it looks up in the DLL.

As a quick and dirty experiment, I hacked some things (see the attachments up
to see if just getting the PrintFunctionNames node into the registry would let
the plug-in work, and it seemed to work. Perhaps with some macro magic that
defines a unique function based on the plug-in name, the connection could be
made that way.

Anyway, that's the extent of what I know about it.  How does this work on
Linux?

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.