search for: _w64

.... My understanding is in general, ssize_t is a 32-bit integer on 32-bit machines, and a 64-bit integer on 64-bit machines. So for Windows, this type definition should vary for 32 and 64-bit machines. A potential implementation would be: #ifdef _WIN64 typedef __int64 ssize_t; #else typedef _w64 int ssize_t; #endif A discussion of "_w64" - http://msdn.microsoft.com/en-us/library/s04b5w00(VS.71).aspx. It's only supported on later versions of Visual Studio, so something like #if !defined(_W64) # if !defined(__midl) && (defined(_X86_) || defined(_M_IX86)) &&a...

...luded from c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\stdio.h:20: In file included from c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\crtdefs.h:74: c:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include\vadefs.h:50:9: error:       unknown type name '__w64' typedef _W64 unsigned int   uintptr_t; My questions: a) Am I referring to the correct C header files folder? b) Do I have to include a Windows specific include file where __w64 is defined? Many thanks in advance. Best regardsUnga -------------- next part -------------- An HTML attachment was...

...fe/trunk/lib/Basic/Targets.cpp?revision=218666&view=markup#l3157 I don't see any obvious bugs here. On Tue, Sep 30, 2014 at 6:50 PM, Eric Mader <emader at gmx.us> wrote: > But crtdefs.h says: > > #ifdef _WIN64 > typedef unsigned __int64 size_t; > #else > typedef _W64 unsigned int size_t; > #endif > > Which conflicts with the built-in definition, that seems to be equivalent > to: > > typedef unsigned int size_t; > > What determines the built-in type of size_t? Is there some setting or > variable I can define to change it? > > Reg...

I believe that we provide a definition of size_t inside the compiler itself when clang is in MSVC compatibility mode. On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote: > I did some more investigation of the size_t size error. I misunderstood > what was happening. It turns out that size_t is already defined before my > prefix header is included. I added the

...64/R.dll] Error 2 Makefile:104: recipe for target 'rbuild' failed make[1]: *** [rbuild] Error 2 Makefile:14: recipe for target 'all' failed make: *** [all] Error 2 After doing some checking (for example see [4]), I asked Duncan about the problem, and he suggested moving the #ifndef _W64 in compat.c up above the offending lines (65-75). That did not work, so, I figured (it seems mistakenly from the other thread) that if those functions are included from stdio already, I can just delete them from compat.c. The specific lines are: int snprintf(char *buffer, size_t max, const char *f...

...9;rbuild' failed >> make[1]: *** [rbuild] Error 2 >> Makefile:14: recipe for target 'all' failed >> make: *** [all] Error 2 >> >> After doing some checking (for example see [4]), I asked Duncan about >> the problem, and he suggested moving the #ifndef _W64 in compat.c up >> above the offending lines (65-75). That did not work, so, I figured >> (it seems mistakenly from the other thread) that if those functions >> are included from stdio already, I can just delete them from compat.c. >> The specific lines are: >> >>...

...;>> make[1]: *** [rbuild] Error 2 >>> Makefile:14: recipe for target 'all' failed >>> make: *** [all] Error 2 >>> >>> After doing some checking (for example see [4]), I asked Duncan about >>> the problem, and he suggested moving the #ifndef _W64 in compat.c up >>> above the offending lines (65-75). That did not work, so, I figured >>> (it seems mistakenly from the other thread) that if those functions >>> are included from stdio already, I can just delete them from compat.c. >>> The specific lines are: &...

...;>> make[1]: *** [rbuild] Error 2 >>> Makefile:14: recipe for target 'all' failed >>> make: *** [all] Error 2 >>> >>> After doing some checking (for example see [4]), I asked Duncan about >>> the problem, and he suggested moving the #ifndef _W64 in compat.c up >>> above the offending lines (65-75). That did not work, so, I figured >>> (it seems mistakenly from the other thread) that if those functions >>> are included from stdio already, I can just delete them from compat.c. >>> The specific lines are: &...