Displaying 10 results from an estimated 10 matches for "d35387".
2018 Apr 10
2
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...ough it depends on a patch to LLD to fix the
> MACH-O linker that is not high enough quality to upstream.
>
> So we have a vested interest in improving the MACH-O linker, and
> in fact a Zig community member has fixed at least one bug in
> MACH-O LLD: reviews.llvm.org/D35387 <http://reviews.llvm.org/D35387>
>
> I don't fully understand how TBD or TAPI works, but I hope that it
> results in improvements to the MACH-O linker.
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at...
2018 Apr 10
3
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...targeting macos
This works today, although it depends on a patch to LLD to fix the MACH-O
linker that is not high enough quality to upstream.
So we have a vested interest in improving the MACH-O linker, and in fact a
Zig community member has fixed at least one bug in MACH-O LLD:
reviews.llvm.org/D35387
I don't fully understand how TBD or TAPI works, but I hope that it results
in improvements to the MACH-O linker.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180410/8d503873/attachment.html>
2018 Apr 10
0
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...it depends on a patch to LLD to fix the MACH-O
>> linker that is not high enough quality to upstream.
>>
>> So we have a vested interest in improving the MACH-O linker, and in fact
>> a Zig community member has fixed at least one bug in MACH-O LLD:
>> reviews.llvm.org/D35387
>>
>> I don't fully understand how TBD or TAPI works, but I hope that it
>> results in improvements to the MACH-O linker.
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>&g...
2018 Apr 10
0
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...orks today, although it depends on a patch to LLD to fix the MACH-O
> linker that is not high enough quality to upstream.
>
> So we have a vested interest in improving the MACH-O linker, and in fact a
> Zig community member has fixed at least one bug in MACH-O LLD:
> reviews.llvm.org/D35387
>
> I don't fully understand how TBD or TAPI works, but I hope that it results
> in improvements to the MACH-O linker.
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mai...
2018 Apr 10
3
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...fix the MACH-O linker that is not high enough quality to
>> upstream.
>>
>> So we have a vested interest in improving the MACH-O linker,
>> and in fact a Zig community member has fixed at least one bug
>> in MACH-O LLD: reviews.llvm.org/D35387
>> <http://reviews.llvm.org/D35387>
>>
>> I don't fully understand how TBD or TAPI works, but I hope
>> that it results in improvements to the MACH-O linker.
>>
>> _______________________________________________
>>...
2018 Sep 20
2
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...>>>> MACH-O linker that is not high enough quality to upstream.
>>>>
>>>> So we have a vested interest in improving the MACH-O linker, and in
>>>> fact a Zig community member has fixed at least one bug in MACH-O LLD:
>>>> reviews.llvm.org/D35387
>>>>
>>>> I don't fully understand how TBD or TAPI works, but I hope that it
>>>> results in improvements to the MACH-O linker.
>>>>
>>>>
>>>> _______________________________________________
>>>> LLVM Developers...
2018 Sep 20
2
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
...that is not high enough quality to upstream.
>>>>>>
>>>>>> So we have a vested interest in improving the MACH-O linker, and in
>>>>>> fact a Zig community member has fixed at least one bug in MACH-O LLD:
>>>>>> reviews.llvm.org/D35387
>>>>>>
>>>>>> I don't fully understand how TBD or TAPI works, but I hope that it
>>>>>> results in improvements to the MACH-O linker.
>>>>>>
>>>>>>
>>>>>> ________________________________...
2018 Apr 10
0
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
> Regardless of any of that, given that TBD files _are_ an integral
part of the apple platform, supporting them is certainly a necessity in
order to have a working apple linker. So, if making LLD work for
Apple/MachO is the justification for adding TBD support to LLVM, that
seems self-evidently a reasonable thing to do. On the other hand, it
looks like the LLD mach-o code is unmaintained
2017 Jul 19
3
[5.0.0 Release] The release branch is open; trunk is now 6.0.0
Dear everyone,
The release branch was recently created from trunk at r308441 and the
trunk version was subsequently incremented to 6.0.0.
Release blockers are tracked by
https://bugs.llvm.org/show_bug.cgi?id=33849 Please mark any bugs, old
or new, that you think need to be fixed before the release as blocking
that.
Please help out with the release by notifying me of any bugs, commits,
or other
2018 Apr 09
2
[cfe-dev] [RFC] Open sourcing and contributing TAPI back to the LLVM community
> On Apr 9, 2018, at 3:23 PM, James Y Knight via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>
> I'm not really clear on the actual benefits of the TBD file, and why Apple migrated to them in the first place. Shouldn't a dynamic library containing only the relevant parts (e.g. the dynamic symbol table) be roughly comparable in size? And, much simpler to support? I assume