[PATCH] Change representation of dllexport/dllimport

[Reid Kleckner]

On Thu, Sep 12, 2013 at 2:43 PM, Nick Lewycky <nlewycky at google.com> wrote:

> Yes, thanks. This is roughly what I was guessing -- a way of encoding the
> exposed symbols list (see tools/gold/gold.exports for an llvm example) in
> the source code.
>
> I do not understand how visibility is orthogonal to dllimport/dllexport. I
> can't think of any way that hidden + dllimport/dllexport makes sense.
> Neither does protected + dllimport, since there is no local copy of the
> symbol to bind to (we're importing it). Protected + dllexport could make
> sense, except that I don't see how it differs from protected (or on a
> regular windows system, dllexport). The only combination that makes sense
> is default + dllimport/dllexport.
>

dllexport is actually closer to protected than default, and that's how ARM
lowers dllexport when targeting ELF.
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dai0242a/BJFHFAHH.html


> Could you give me an example where you'd actually want to use these
> visibilities in combination?
>
> Nick
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130912/9dd03e7f/attachment.html>