[PATCH] D33041: [ELF] - Set DF_STATIC_TLS flag for x86_64 target.

[Rui Ueyama via llvm-commits]

It is cheap to do, I'm not opposed to adding that flag, and just wondering
how the flag is consumed.

If the runtime doesn't recognize the flag, it is nice to improve it to
print out a user-friendly error message so that you don't need to use
readelf to figure out what is going on when something goes wrong.

On Wed, May 10, 2017 at 1:46 PM, Joerg Sonnenberger via llvm-commits <
llvm-commits at lists.llvm.org> wrote:

> On Wed, May 10, 2017 at 01:32:29PM -0700, Rui Ueyama via llvm-commits
> wrote:
> > Do they actually use this as a diagnostic hint to print out a
> user-friendly
> > error message?
>
> No, but it makes it much easier to tell with readelf or so that it is
> necessary. Otherwise you have to look for the relocation list and that's
> platform specific. If it is cheap to do, create the flag. If it requires
> a scan of the relocation list, it might not be worth it.
>
> Joerg
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170510/7c884afe/attachment.html>