Displaying 3 results from an estimated 3 matches for "5b4417f5".
2011 May 23
0
[LLVMdev] [cfe-dev] __builtin_va_list different on targets
...>
> However, other targets may have more complicated differences than
> just void* vs. char*.
>
> John.
>
--
Best regards,
Wen-Han
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110523/5b4417f5/attachment.html>
2011 May 23
2
[LLVMdev] __builtin_va_list different on targets
Hi all,
I know __builtin_va_list is target-specific, and
ARM has typedef void* __builtin_va_list;
X86 has typedef char* __builtin_va_list;
It seems they can be treated as the same prototype,i.e.. void*, at the
header level.
What I want to ask is:
If I write a program use "typedef *void** __builtin_va_list" on X86, and run
it.
Would I face any problem on run-time?
I think it won't
2011 May 23
1
[LLVMdev] [cfe-dev] __builtin_va_list different on targets
On May 22, 2011, at 8:49 PM, Wenhan Gu wrote:
> I know __builtin_va_list is target-specific, and
> ARM has typedef void* __builtin_va_list;
> X86 has typedef char* __builtin_va_list;
>
>
> It seems they can be treated as the same prototype,i.e.. void*, at the header level.
> What I want to ask is:
>
> If I write a program use "typedef void*