search for: misdeclar

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

...ously have compile-time problems, though: for example, in C, if va_list is a void*, then it can be implicitly converted to any pointer type instead of (as with char*) only explicitly converted; and in C++, you can get different manglings, which is actually how we found out that our ARM target was misdeclaring it. But otherwise it should be fine, as long as that's the only difference. However, other targets may have more complicated differences than just void* vs. char*. John. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llv...

...roblems, though: for example, > in C, if va_list is a void*, then it can be implicitly converted to any > pointer > type instead of (as with char*) only explicitly converted; and in C++, you > can get different manglings, which is actually how we found out that our > ARM target was misdeclaring it. But otherwise it should be fine, as long > as that's the only difference. > > However, other targets may have more complicated differences than > just void* vs. char*. > > John. > -- Best regards, Wen-Han -------------- next part -------------- An HTML attachmen...

These are the files from the swig/classes/include directory. I hope the line endings don''t end up wrong. _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users