Displaying 6 results from an estimated 6 matches for "vadef".
Did you mean:
vdef
2015 Apr 26
3
[LLVMdev] How to compile a simple C program with clang on Windows 8.1?
...st1.exe
In file included from test1.c:2:
In file included 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
------------...
2016 Dec 09
10
RFC: Adding argument allocas
...benefit of doing this is that it would make it
possible to implement va_start by taking the address of a parameter and
doing pointer arithmetic. While that code is fairly invalid, it’s exactly
what the MSVC STL headers do for 32-bit x86. If we make this work in Clang,
we can remove our stdarg.h and vadefs.h wrapper headers. Users often pass
flags that cause clang to skip these wrapper headers, and then they file
bugs complaining that va lists don't work.
At the end of the day, this feels like a straightforward engineering
improvement to LLVM, and it feels worth doing to me. Does anyone feel
ot...
2016 Dec 28
0
RFC: Adding argument allocas
...s is that it would make it
> possible to implement va_start by taking the address of a parameter and
> doing pointer arithmetic. While that code is fairly invalid, it’s exactly
> what the MSVC STL headers do for 32-bit x86. If we make this work in Clang,
> we can remove our stdarg.h and vadefs.h wrapper headers. Users often pass
> flags that cause clang to skip these wrapper headers, and then they file
> bugs complaining that va lists don't work.
>
> At the end of the day, this feels like a straightforward engineering
> improvement to LLVM, and it feels worth doing to...
2016 Dec 10
0
RFC: Adding argument allocas
...that it would
> make it possible to implement va_start by taking the address of a
> parameter and doing pointer arithmetic. While that code is fairly
> invalid, it’s exactly what the MSVC STL headers do for 32-bit x86.
> If we make this work in Clang, we can remove our stdarg.h and
> vadefs.h wrapper headers. Users often pass flags that cause clang to
> skip these wrapper headers, and then they file bugs complaining that
> va lists don't work.
> At the end of the day, this feels like a straightforward engineering
> improvement to LLVM, and it feels worth doing to me....
2016 Dec 10
0
llvm-dev Digest, Vol 150, Issue 37
...mplement va_start by taking the address of a
> > > parameter and doing pointer arithmetic. While that code is fairly
> > > invalid, it’s exactly what the MSVC STL headers do for 32-bit x86.
> > > If
> > > we make this work in Clang, we can remove our stdarg.h and vadefs.h
> > > wrapper headers. Users often pass flags that cause clang to skip
> > > these
> > > wrapper headers, and then they file bugs complaining that va lists
> > > don't work.
> >
> > This ignores the other reason why this doesn't work at the...
2016 Dec 09
6
RFC: Adding argument allocas
...ld make it
>> possible to implement va_start by taking the address of a parameter and
>> doing pointer arithmetic. While that code is fairly invalid, it’s exactly
>> what the MSVC STL headers do for 32-bit x86. If we make this work in Clang,
>> we can remove our stdarg.h and vadefs.h wrapper headers. Users often pass
>> flags that cause clang to skip these wrapper headers, and then they file
>> bugs complaining that va lists don't work.
>>
>
> This ignores the other reason why this doesn't work at the moment: reading
> off the end of an all...