[LLVMdev] RFC: auto-linking IR proposal

Daniel Dunbar daniel at zuster.org
Wed Jan 16 16:01:51 PST 2013

On Wed, Jan 16, 2013 at 3:28 PM, Gao, Yunzhong <Yunzhong.Gao at am.sony.com>wrote:

> Hi Daniel,
> >> My understanding of the Microsoft #pragma comment(lib, ...) semantics
> 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).
> > 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 means the dependent library feature is also
> deprecated.
> To clarify, at one point LLVM IR had a way to list dependent libraries in
> the form of
> deplibs = [ "blah.lib", "foo.lib" ]
> This feature was later removed in llvm commit r168694, which is what I
> referred to as being deprecated. i.e., I was not saying that the MSVC
> defaultlib flag is being deprecated.

Ah, yes! I had completely forgotten about that.

Unlike that feature, which had some semantics the IR would try to handle
(it could be used to reference libraries of bitcode the IR linker would try
and handle), the expectation is that the IR layers will not inspect or
otherwise manipulate the Linker Options flags other than to merge them
following the module flags behavior.

 - Daniel

> - Gao.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130116/a0be9596/attachment.html>

More information about the llvm-dev mailing list