[lld] r195091 - Creating release_34 branch

Michael Spencer bigcheesegs at gmail.com
Thu Nov 21 16:32:28 PST 2013


On Thu, Nov 21, 2013 at 3:42 PM, Bill Wendling <isanbard at gmail.com> wrote:
> On Nov 21, 2013, at 2:55 PM, Rui Ueyama <ruiu at google.com> wrote:
>
> On Thu, Nov 21, 2013 at 2:47 PM, Shankar Easwaran <shankare at codeaurora.org>
> wrote:
>>
>> Hi Rui,
>>
>>
>> On 11/21/2013 4:25 PM, Rui Ueyama wrote:
>>>
>>> Yeah, I'm skeptical about a real value of including the LLD in the 3.4
>>> release. The linker is not still useful. Also, when the branch was cut,
>>> there was a critical bug in the LLD that it couldn't link a large
>>> executable if it contains too many relocations, but I don't think we want
>>> to cherry pick the fix and maintain the release branch.
>>
>> The RoundTrip YAML/Native passes are only run in DEBUG mode. lld still
>> should link a large executable like itself without the patch in release
>> mode. Am I missing something ?
>
>
> Ah, that's a good point. So, yeah, the LLD can link large programs. I stand
> corrected. :)
>
>
> Whether we submit binaries for it is one question. But I do like having all
> of the main projects branched when we do a release. I’ve been asked to do
> this before and it’s not a bad idea. It marks a point in time when the
> projects were in sync. :-)
>
> -bw

Ah, the branching is fine. This commit just made me think about the
actual release.

- Michael Spencer




More information about the llvm-commits mailing list