search for: istargetwin64

...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 "msvc-compabile" - isTargetWin32() which means "everything on windows", so Windows + Mingw + Cygwin - isTargetWin64() is is basically 64-bit version of isTargetWin32(), but strictly speaking is slightly different This naming while being the historical artifact is extremely confusing. For me it seems the best solution will be something like this: - isTargetMingw() - with obvious meaning - isTargetMSVC() - with...

...s "msvc-compabile" > - isTargetWin32() which means "everything on windows", so Windows + > Mingw + Cygwin Minor correction: currently isTargetWin32 means 32-bits (not "everything"), Windows + Mingw, not Cygwin. So this is actually even more confusing... > - isTargetWin64() is is basically 64-bit version of isTargetWin32(), > but strictly speaking is slightly different > > This naming while being the historical artifact is extremely > confusing. For me it seems the best solution will be something like > this: > - isTargetMingw() - with obvious mea...

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

Hi! when reading X86Subtarget.h the methods seem a bit disordered, therefore I would propose to sort them new: -getTargetTriple() -cpu features (e.g. hasSSE1()) -os types (e.g. isTargetDarwin()) -object types (e.g. isTargetELF()) -callconv related functions (e.g. isTargetWin64(), consider renaming to isCallConvWin64(), getStackAlignment()) -pic functions perhaps my problem of generating elf objects on windows can be easily solved by creating a new os type, just like mingw and cycwin, and patching X86Subtarget.h accordingly (of course only in my private copy, i dou...

...ing > Just to make stuff clear: I just wanted proper naming which will be > non-confusing. Right now we have: > - isTargetWindows() which really means "msvc-compabile" > - isTargetWin32() which means "everything on windows", so Windows + > Mingw + Cygwin > - isTargetWin64() is is basically 64-bit version of isTargetWin32(), > but strictly speaking is slightly different > > This naming while being the historical artifact is extremely > confusing. For me it seems the best solution will be something like > this: > - isTargetMingw() - with obvious mea...

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 > libraries on windows, but if you want true compatibility with the full > platform > those ABIs