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

Hello! http://gcc.gnu.org/ml/gcc-help/2012-05/msg00043.html ping? -- Regards,   niXman ___ Dual-target(i686/x86_64) MinGW compiler for i686/x86_64 hosts:   http://sourceforge.net/projects/mingwbuilds/

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

2012/5/24 niXman : > Hello! > > http://gcc.gnu.org/ml/gcc-help/2012-05/msg00043.html > > ping? > > > -- > Regards, >   niXman There is no option to disable this, as thiscall is part of the Windows ABI. But you can switch via that -mabi=(sysv|ms) option. Regards, Kai

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

2012/5/24 Kai Tietz: > There is no option to disable this, as thiscall is part of the Windows > ABI. Could you please tell me, in what revision is added this change, so that I could have made the reverting patch? > But you can switch via that -mabi=(sysv|ms) option. I.e. '-mabi = ms' is now used

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

2012/5/24 niXman : > 2012/5/24 Kai Tietz: >> There is no option to disable this, as thiscall is part of the Windows >> ABI. > > Could you please tell me, in what revision is added this change, so > that I could have made the reverting patch? Hmm, no idea. see revision history on svn for that. Ou

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

2012/5/24 Kai Tietz: > Hmm, no idea.  see revision history on svn for that.  Out of > curiousity, for what reason you want to revert this patch locally for > you? Because of the mismatch of the calling-convention between MinGW and Clang: http://llvm.org/bugs/show_bug.cgi?id=12684 Thank you for you

RMS to present at the Cauldron

For those of you attending the Cauldron meeting in Prague in July, RMS will be in town and will come by to give a talk on the first day of the meeting. See you there!

[gimplefe] Merge from trunk, preparation for gimple testsuite

I've merged trunk into gimple-front-end (rev 187836). I've added a manifest file to use with contrib/testsuite-management/validate_failures.py. Sandeep, this will be useful when we start having more gimple tests (see http://gcc.gnu.org/wiki/Testing_GCC#Using_validate_failures.py). You can

error: call of overloaded ‘foo(int)’ is ambiguous (0 vs null ptr)

Hello, I'm not sure whether this is standard behaviour or not; nonetheless I was quite surprised: 8<8<8< void foo(long); void foo(const char*); void bar() { foo(0); foo(0+0); // ! foo(1-1); // ! foo(1); } 8<8<8< The first call t

Re: error: call of overloaded ‘foo(int)’ is ambiguous (0 vs null ptr)

On Thu, May 24, 2012 at 2:26 PM, Peter A. Felvegi wrote: > Hello, this list is not the appropriate place to discuss this. Check a C++ forum. > > I'm not sure whether this is standard behaviour or not; nonetheless I was > quite surprised: Welcome to null pointer constant madness. It is standard

Re: error: call of overloaded ‘foo(int)’ is ambiguous (0 vs null ptr)

On 24 May 2012 20:26, Peter A. Felvegi wrote: > Hello, > > I'm not sure whether this is standard behaviour or not; nonetheless I was > quite surprised: Please note that "is this valid" questions are not appropriate on this mailing list, please use the gcc-help mailing list for questions about usin

gcc-4.5-20120524 is now available

Snapshot gcc-4.5-20120524 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20120524/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.5 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: Status of the PPH implementation

Geez, we can't attach pdf files on message to the list. The document is at: http://gcc.gnu.org/wiki/pph?action=AttachFile&do=view&target=pph-in-gcc.pdf Diego.