search for: r168694

...rary will be converted into a directive that starts with >> "/DEFAULTLIB" in the COFF .drectve section. To demonstrate, the following patch >> produces directives that work with Visual Studio 2010 using the now-deprecated >> dependent library feature (commits r168779 and r168694). > Is that feature now-deprecated? The documentation here: > http://msdn.microsoft.com/en-us/library/7f0aews7.aspx > only talks about the "exestr" comment type being deprecated. > I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to...

...ibrary will be converted into a directive that starts with > "/DEFAULTLIB" in the COFF .drectve section. To demonstrate, the following > patch > produces directives that work with Visual Studio 2010 using the > now-deprecated > dependent library feature (commits r168779 and r168694). > Is that feature now-deprecated? The documentation here: http://msdn.microsoft.com/en-us/library/7f0aews7.aspx only talks about the "exestr" comment type being deprecated. I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to me that that...

...is that each specified library will be converted into a directive that starts with "/DEFAULTLIB" in the COFF .drectve section. To demonstrate, the following patch produces directives that work with Visual Studio 2010 using the now-deprecated dependent library feature (commits r168779 and r168694). /* beginning of patch */ Index: /home/ygao/LLVM/llvm/lib/Target/X86/X86AsmPrinter.cpp =================================================================== --- /home/ygao/LLVM/llvm/lib/Target/X86/X86AsmPrinter.cpp (revision 165914) +++ /home/ygao/LLVM/llvm/lib/Target/X86/X86AsmPrinter.cpp...

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