David, Sorry the previous email was to the thread, this link is to the
exact email where I detail the problem.
https://sourceware.org/ml/binutils/2017-08/msg00123.html

On Fri, Aug 18, 2017 at 7:46 PM, Martell Malone <martellmal...@gmail.com>
wrote:

> David, I also want to remove KEEP (*(.ctors)); which seems to cause a bug
> when linking in conjunction with KEEP (*(SORT_BY_NAME(.ctors.*))) and our
> new mingw-w64 markers. I have details in this email on binutils ml.
> https://sourceware.org/ml/binutils/2017-08/msg00078.html
> I have to create a minified test case for this to get approval to remove
> that line.
>
> Martin, I am fine with adding a __clang__ guard around the implementation
> if we want to land it now rather then keeping it out of tree?
> Kai any objections?
>
> On Fri, Aug 18, 2017 at 7:36 PM, Martin Storsjö <mar...@martin.st> wrote:
>
>> On Fri, 18 Aug 2017, Martell Malone wrote:
>>
>>  suddenly requiring the absolutely latest binutils, right?
>>>>>
>>>>
>>> Correct we will need the next binutils release as a min version.
>>> I don't think we need a condition we should just specify a new min
>>> binutils
>>> version for mingw-w64 to require.
>>> jon_y said this to me in the past, I think we should wait until all your
>>> crt patch changes land in tree first though incase someone wanted to
>>> make a
>>> v6 branch before this hits master.
>>>
>>
>> I disagree with this plan. I want the mingw/clang support upstreamed,
>> requiring zero patches on clang/lld and mingw. It won't be perfect
>> immediately, but I'd rather have it somewhat functional, to make it easier
>> for others to test, use and improve upon, instead of keeping the patches
>> outside of the main repo like for the last two years.
>>
>> The missing patches for an absolute MVP working clang/mingw are this one
>> and the lld frontend.
>>
>> I don't want to postpone that any further, waiting for a new binutils
>> release with some change that isn't even merged yet, while striving for
>> perfection. That's obviously the end goal, but let's not have that stop us
>> from having a sensible compromise in the meantime.
>>
>>
>> // Martin
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to