Duncan Sands 0397cd2ec4 When simplifying a call to a bitcast function, tighten up ... the conditions for performing the transform when only the function declaration is available: no longer allow turning i32 into i64 for example. Only allow changing between pointer types, and between pointer types and integers of the same size. For return values ptr -> intptr was already allowed; I added ptr -> ptr and intptr -> ptr while there. As shown by a recent objc testcase, changing the way parameters/return values are passed can be fatal when calling code written in assembler that directly manipulates call arguments and return values unless the transform has no impact on the way they are passed at the codegen level. While it is possible to imagine an ABI that treats integers of pointer size differently to pointers, I don't think LLVM supports any so the transform should now be safe while still being useful. llvm-svn: 51834		2008-06-01 07:38:42 +00:00
clang	Tweak Sema::ObjCQualifiedIdTypesAreCompatible() to handle qualified interface types on the RHS.	2008-06-01 02:43:50 +00:00
llvm	When simplifying a call to a bitcast function, tighten up	2008-06-01 07:38:42 +00:00