[LLVMdev] Switching to the new MingW ABI

[Anton Korobeynikov]

+1.

In case of ARM e.g. we can make sure we won't link stuff with
incompatible ABIs, but not here....

On Tue, Dec 10, 2013 at 5:28 AM, Reid Kleckner <rnk at google.com> wrote:
> It's worth noting that gcc chose *not* to support any ABI changing flags.
>
> I'm in favor of avoiding flags here.  We can simply document that clang 3.3
> and earlier works with gcc 4.6 and earlier, and clang 3.4+ works with gcc
> 4.7+.
>
>
> On Mon, Dec 9, 2013 at 5:18 PM, Rafael Espíndola
> <rafael.espindola at gmail.com> wrote:
>>
>> Mingw switched abis with the release of gcc 4.7
>> (http://gcc.gnu.org/gcc-4.7/changes.html). The main change is that now
>> mingw (like msvc) given thiscall calling convention to methods by
>> default.
>>
>> I think the last bug blocking us to support the new abi has just been
>> fixed. The question now is how to switch.
>>
>> The attached patches simply switch llvm and clang to the new ABI. This
>> is similar to what gcc did on 4.7. The timing is also good as we will
>> not build with 4.6 anymore when we switch to c++11.
>>
>> Is anyone depending on targeting the 4.6 mingw ABI even after we drop
>> support for building with 4.6?
>>
>> Cheers,
>> Rafael
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>



-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University