This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: PaweÅ Sikora <pluto at agmk dot net>
To: gcc-help at gcc dot gnu dot org
Cc: JonY <jon_y at users dot sourceforge dot net>, niXman <i dot nixman at gmail dot com>
Date: Sat, 12 May 2012 20:29:12 +0200
Subject: Re: how to disable __thiscall on MinGW-gcc-4.7.x ?
References: <CAMPTgK2q8LJ_5VXLuPwyKnaY7ErWaD_n2wW9b3kTpACcVYzCHg@mail.gmail.com> <CAMPTgK2LgGRT_M8_kfeLDuJaVuoZQi4H_Cznk8LtM=S1v-fuAQ@mail.gmail.com> <4FAE7AFD.6000805@users.sourceforge.net>

On Saturday 12 of May 2012 23:00:13 JonY wrote:
> On 5/9/2012 21:33, niXman wrote:
> > 2012/5/9 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.

Follow-Ups:
- Re: how to disable __thiscall on MinGW-gcc-4.7.x ?
  - From: niXman

References:
- how to disable __thiscall on MinGW-gcc-4.7.x ?
  - From: niXman
- Re: how to disable __thiscall on MinGW-gcc-4.7.x ?
  - From: niXman
- Re: how to disable __thiscall on MinGW-gcc-4.7.x ?
  - From: JonY

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]