llvm dev - Dec 2017 - llvm-dev Digest, Vol 162, Issue 35

>Keeping the shared library build working's probably a fine idea, though
>working around GCC bugs (depending on how ubiquitous they are) might be
>less so.
FWIW.

I would say I know quite a bit about both issues (GCC issues handling for LLVM
builds and
using LLVM as shared libraries), but at least we have a fix for GCC in LLD code
:
https://github.com/llvm-mirror/lld/blob/master/ELF/InputSection.cpp#L687

and also a bug that currently requires shared build to work 
(https://bugs.llvm.org//show_bug.cgi?id=35536) for testing atm.

George.

>>Keeping the shared library build working's probably a fine idea,
though
>>working around GCC bugs (depending on how ubiquitous they are) might be
>>less so.
>
>FWIW.
>
>I would say I know quite a bit about both issues (GCC issues handling for
LLVM builds and
>using LLVM as shared libraries), but at least we have a fix for GCC in LLD
code :
>https://github.com/llvm-mirror/lld/blob/master/ELF/InputSection.cpp#L687
>
>and also a bug that currently requires shared build to work
>(https://bugs.llvm.org//show_bug.cgi?id=35536) for testing atm.
>
>George.
For GCC probably better example in LLD code is
https://github.com/llvm-mirror/lld/blob/master/ELF/SyntheticSections.cpp#L1782,
we are workaround compilation issue there.

But anyways I am just learning here too, so sharing some points I know only.

George.