Chandler Carruth c933221826 Factor out (some of) the checking for invalid forms of pointer ... arithmetic into a couple of common routines. Use these to make the messages more consistent in the various contexts, especially in terms of consistently diagnosing binary operators with invalid types on both the left- and right-hand side. Also, improve the grammar and wording of the messages some, handling both two pointers and two (different) types. The wording of function pointer arithmetic diagnostics still strikes me as poorly phrased, and I worry this makes them slightly more awkward if more consistent. I'm hoping to fix that with a follow-on patch and test case that will also make them more helpful when a typedef or template type parameter makes the type completely opaque. Suggestions on better wording are very welcome, thanks to Richard Smith for some initial help on that front. llvm-svn: 133906		2011-06-27 08:02:19 +00:00
clang	Factor out (some of) the checking for invalid forms of pointer	2011-06-27 08:02:19 +00:00
compiler-rt	<rdar://problem/9624306> clean up darwin platform to use xcrun. Set up variables in darwin_bni.mk. Use GetCNAVar in AppleBI.mk	2011-06-21 00:07:55 +00:00
debuginfo-tests	Testcase for r133065	2011-06-15 17:57:23 +00:00
libcxx	test for pair piecewise construction	2011-06-22 23:51:19 +00:00
libcxxabi	In cxa_demangle.cpp, rewrite __parse_unresolved_name to reflect updated understanding and sync with updated clang mangling. Also fix think-o in __parse_encoding enabling the parsing of trailing .eh and .b.	2011-06-22 19:27:39 +00:00
lldb	Move more top level test dirs to reside under functionalities dir.	2011-06-26 21:36:28 +00:00
llvm	Teach one piece of scalarrepl to handle lifetime markers. When transforming an	2011-06-27 05:40:02 +00:00
polly	www: Adding webpage to track memory access transformation	2011-06-18 17:17:16 +00:00