how to disable __thiscall on MinGW-gcc-4.7.x ?

[niXman]

Hello list!

According to the changes in the gcc-4.7.0 [1]: Windows x86 targets are
using the __ thiscall calling convention for C++ class-member
functions.

The question is how to disable this?

Thanks.

[1] http://gcc.gnu.org/gcc-4.7/changes.html

[Václav Zeman]

Post by niXman
Hello list!
According to the changes in the gcc-4.7.0 [1]: Windows x86 targets are
using the __thiscall calling convention for C++ class-member
functions.
The question is how to disable this?

It is the platforms ABI, why would you want to disable it?

Post by niXman
Thanks.
[1] http://gcc.gnu.org/gcc-4.7/changes.html

[niXman]

Post by Václav Zeman
It is the platforms ABI, why would you want to disable it?

If it is the platforms ABI, why before version 4.7.x this was not required?
I do not want to use the thiscall in 4.7.x version, and the next versions.

[niXman]

ping?

[JonY]

Post by niXman

Post by Václav Zeman
It is the platforms ABI, why would you want to disable it?

If it is the platforms ABI, why before version 4.7.x this was not required?
I do not want to use the thiscall in 4.7.x version, and the next versions.

This is an ABI change, a move to make GCC closer to C++ ABI on Windows
(namely MSVC).

[Paweł Sikora]

Post by JonY

Post by niXman

Post by Václav Zeman
It is the platforms ABI, why would you want to disable it?

If it is the platforms ABI, why before version 4.7.x this was not required?
I do not want to use the thiscall in 4.7.x version, and the next versions.

This is an ABI change, a move to make GCC closer to C++ ABI on Windows
(namely MSVC).

are there any benefits from this move? iirc gcc users can't call msvc-c++
parts directly due to different objects layout and name mangling.

[niXman]

Post by Paweł Sikora
are there any benefits from this move? iirc gcc users can't call msvc-c++
parts directly due to different objects layout and name mangling.

In this case, I do not understand the meaning in __ thiscall by default.
Also, I do not understand why this feature is not disabled. Someone
must have enabled it. How can I disable it?

[JonY]

Post by niXman

Post by Paweł Sikora
are there any benefits from this move? iirc gcc users can't call msvc-c++
parts directly due to different objects layout and name mangling.

There is an ongoing effort to make them compatible, though not any time
soon, this is one of the first steps.

Post by niXman
In this case, I do not understand the meaning in __ thiscall by default.
Also, I do not understand why this feature is not disabled. Someone
must have enabled it. How can I disable it?

I don't think it can be disabled. You should revert to an older version
compatible with your compiled libraries.

As a side note, C++ is a very complex language, you should not assume
the objects are compatible if you mix compilers, even if it's a
different version of the same compiler.