[PATCH] Change representation of dllexport/dllimport
Reid Kleckner
rnk at google.com
Mon Sep 9 13:13:24 PDT 2013
On Mon, Sep 9, 2013 at 11:06 AM, Anton Korobeynikov <anton at korobeynikov.info
> wrote:
> > Why do you say that dllimport could be any visibility? Is it useful
> to have a visibility(non-hidden) + dllimport symbol?
> Because dllimport has nothing wrt the visibility. Visibility is
> essnetially ELF'ish thing. dllexport can be thought as "default"
> visibility and everything else is hidden visibility by default, but
> dllimport does not fit into this semantics. Trying to fit them into
> visibility is essentialy a workaround
Right, one cannot map dllimport to an existing visibility. But since it
doesn't make sense to combine any other visibility with dllimport, it seems
like you could create a new LLVM visibility value for dllimport that
doesn't map to ELF visibility.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130909/8640ea48/attachment.html>
More information about the llvm-commits
mailing list