search for: hasdllexportlinkag

Displaying 3 results from an estimated 3 matches for "hasdllexportlinkag".

Did you mean: hasdllexportlinkage
2013 Jan 16
0
[LLVMdev] RFC: auto-linking IR proposal
...M.lib_end(); + I != E; ++I) { + name = " /DEFAULTLIB:\""; + name += *I; + name += "\""; + OutStreamer.EmitBytes(name, 0); + } + } + for (Module::const_iterator I = M.begin(), E = M.end(); I != E; ++I) if (I->hasDLLExportLinkage()) DLLExportedFns.push_back(Mang->getSymbol(I)); /* end of patch */ I am currently looking for advice on what is the correct approach to re-implement #pragma comment(lib, ...) with Clang/LLVM. A mingw linker (at least the one that I played with) just ignores this directive with no w...
2013 Jan 16
2
[LLVMdev] RFC: auto-linking IR proposal
...+ name = " /DEFAULTLIB:\""; > + name += *I; > + name += "\""; > + OutStreamer.EmitBytes(name, 0); > + } > + } > + > for (Module::const_iterator I = M.begin(), E = M.end(); I != E; ++I) > if (I->hasDLLExportLinkage()) > DLLExportedFns.push_back(Mang->getSymbol(I)); > > /* end of patch */ > > I am currently looking for advice on what is the correct approach to > re-implement #pragma comment(lib, ...) with Clang/LLVM. > > A mingw linker (at least the one that I played with)...
2013 Jan 15
4
[LLVMdev] RFC: auto-linking IR proposal
Hi all, We plan to add some auto-linking support for Mach-O, and need a scheme for encoding this information in the LLVM IR. We would like the same scheme to be able to support Microsoft's #pragma comment(lib,...) and #pragma comment(library, ...) features eventually. The current proposal is as follows: -- #1. Extend module-level metadata flags (llvm.module.flags) to support two new