similar to: [LLVMdev] Handling SRet on Windows x86...

On Mar 28, 2013, at 1:35 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: Oscar, just FYI, your wording is very strong, and that is often not the most productive way to make your point. That said, to address some of the things you've raised in a couple of threads: >> If you think these are irrelevant points then you need to state why >> and should back it up with less

Hi Eric, > From my perspective Win32 is the windows ABI and mingw and cygwin are their own ABIs No. They are using Windows Platform ABI for almost everything (e.g. calling API, C runtime, etc.). At least mingw does. The differences are exactly in unspecified area (e.g. passing / returning structs by value). The only difference is C++, where mingw / cygwin follows Itanium ABI and MSVC - its

The Wine development release 1.5.28 is now available. What's new in this release (see below for details): - GnuTLS used for all secure connections, OpenSSL is no longer needed. - Mac driver enabled by default. - Built-in FixedSys fonts. - New icon for the joystick control panel. - Postscript driver improvements. - Various bug fixes. The source is available from the following

On Thu, Mar 28, 2013 at 8:55 AM, Reid Kleckner <rnk at google.com> wrote: > On Thu, Mar 28, 2013 at 8:22 AM, Joe Groff <arcata at gmail.com> wrote: > >> On Wed, Mar 27, 2013 at 8:15 PM, Chandler Carruth <chandlerc at google.com>wrote: >> >>> This is why I suggest that the Windows ABI is whatever MSVC happens to >>> do. The mingw ABI happens to

On Thu, Mar 28, 2013 at 3:19 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Eric Christopher <echristo at gmail.com> writes: > >> In my opinion none of these are irrelevant. Mingw and cygwin are separate >> ABIs that deal with some C compatibility (problems mentioned in this thread >> are important here too) and give you the ability to work with low level C

On Wed, Mar 27, 2013 at 8:15 PM, Chandler Carruth <chandlerc at google.com>wrote: > This is why I suggest that the Windows ABI is whatever MSVC happens to do. > The mingw ABI happens to consist of a conjunction of what MSVC does for C > and what GCC on Linux does for C++. That is a unique and different ABI, and > I don't think you can reasonably call it *just*

On Thu, Mar 28, 2013 at 8:22 AM, Joe Groff <arcata at gmail.com> wrote: > On Wed, Mar 27, 2013 at 8:15 PM, Chandler Carruth <chandlerc at google.com>wrote: > >> This is why I suggest that the Windows ABI is whatever MSVC happens to >> do. The mingw ABI happens to consist of a conjunction of what MSVC does for >> C and what GCC on Linux does for C++. That is a

Hi Oscar, >> MSVC is not the system compiler. Certainly, it is not distributed with > >> the system. Actually, MSVC was a secondary player on Windows for a long > >> time, with several other C++ ABI-incompatible options available. > > > > > > It isn't shipped with the system, but it's freely available as part of > the > > Windows SDK,

On Thu, Mar 28, 2013 at 12:19 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > What do you mean by "the full platform"? Every propietary extension that > MS came with along all these years? (From structured exceptions to > whatever Windows RT requires?) > > MinGW is very well capable of using the Win32 API. There is partial or > non-existent support for extensions

On Wed, Mar 27, 2013 at 2:28 PM, Anton Korobeynikov <asl at math.spbu.ru>wrote: > Hi Eric, > > > From my perspective Win32 is the windows ABI and mingw and cygwin are > their own ABIs > No. They are using Windows Platform ABI for almost everything (e.g. > calling API, C runtime, etc.). At least mingw does. The differences > are exactly in unspecified area (e.g.

Hi Anton, >From my perspective Win32 is the windows ABI and mingw and cygwin are their own ABIs especially as we're not targeting the MSVC abi, it's just the windows abi? -eric On Wed, Mar 27, 2013 at 1:32 PM, Anton Korobeynikov <asl at math.spbu.ru>wrote: > Hi Timur, > > I myself find the name "Win32" pretty confusing and easy to misuse > (especially

2013/3/27 Anton Korobeynikov <asl at math.spbu.ru>: > Hi Eric, > >> From my perspective Win32 is the windows ABI and mingw and cygwin are their own ABIs > No. They are using Windows Platform ABI for almost everything (e.g. > calling API, C runtime, etc.). At least mingw does. The differences > are exactly in unspecified area (e.g. passing / returning structs by >

2013/3/20 Timur Iskhodzhanov <timurrrr at google.com>: > Anton, > > [+Eric, Nick, > the e-mail thread context has been broken a few times, so you should > probably look at the llvmdev archives. > It all starts here: > http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-October/053961.html ] > > So I've decided to make a new attempt to fix this issue. > >

Let's go directly to the example struct S { double dummy1; double dummy2; }; S bar(); S foo() { return bar(); } This is the result of g++ -c -S -O2 (focus on the final `ret'): __Z3foov: LFB0: pushl %ebp LCFI0: movl %esp, %ebp LCFI1: pushl %ebx LCFI2: subl $20, %esp LCFI3: movl 8(%ebp), %ebx movl %ebx, (%esp) call __Z3barv pushl %eax movl %ebx, %eax movl -4(%ebp), %ebx

2013/3/28 Anton Korobeynikov <asl at math.spbu.ru>: >> How can having an MSVC compatible compiler be to the detriment of clang and >> llvm? No one is trying to break mingw here, merely add support for something > Just to make stuff clear: I just wanted proper naming which will be > non-confusing. Right now we have: > - isTargetWindows() which really means

Anton, [+Eric, Nick, the e-mail thread context has been broken a few times, so you should probably look at the llvmdev archives. It all starts here: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-October/053961.html ] So I've decided to make a new attempt to fix this issue. We've discussed my patches with Eric and came up with the following idea: a) IsTargetWindows should be true for

Anton, What do you think? 2013/3/20 Eric Christopher <echristo at gmail.com>: > > > > On Wed, Mar 20, 2013 at 5:21 PM, Timur Iskhodzhanov <timurrrr at google.com> > wrote: >> >> 2013/3/20 Timur Iskhodzhanov <timurrrr at google.com>: >> > Anton, >> > >> > [+Eric, Nick, >> > the e-mail thread context has been broken a

On Thu, Mar 28, 2013 at 12:19 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > Eric Christopher <echristo at gmail.com> writes: > > > In my opinion none of these are irrelevant. Mingw and cygwin are separate > > ABIs that deal with some C compatibility (problems mentioned in this > thread > > are important here too) and give you the ability to work with low

The Wine development release 1.7.47 is now available. What's new in this release (see below for details): - Text drawing in Direct2D. - Support for the new thread pool API. - Toolbar state saving. - Beginnings of an implementation for proper HID support. - Support for file objects in device drivers. - Various bug fixes. The source is available from the following locations:

On Wed, Mar 20, 2013 at 5:21 PM, Timur Iskhodzhanov <timurrrr at google.com>wrote: > 2013/3/20 Timur Iskhodzhanov <timurrrr at google.com>: > > Anton, > > > > [+Eric, Nick, > > the e-mail thread context has been broken a few times, so you should > > probably look at the llvmdev archives. > > It all starts here: > >